branch: elpa/pg
commit 2cc7623275a1166777e48ad3e72d05d0f1a02fbc
Author: Eric Marsden <eric.mars...@risk-engineering.org>
Commit: Eric Marsden <eric.mars...@risk-engineering.org>
Update information on tested variant versions
---
README.md | 32 ++++++++++++++++----------------
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/README.md b/README.md
index f3b12f9b43..99eac6e336 100644
--- a/README.md
+++ b/README.md
@@ -81,12 +81,12 @@ The following PostgreSQL-compatible databases have been
tested:
hosts (AGPLv3 licence). Works perfectly (last tested 2025-05 with Citus
version 13.0).
- The [OrioleDB](https://github.com/orioledb/orioledb) extension, which adds a
new storage engine
- designed for better multithreading and solid state storage, works perfectly.
Last tested 2025-04
- with version beta10.
+ designed for better multithreading and solid state storage, works perfectly.
Last tested 2025-07
+ with version beta11.
- The [Microsoft DocumentDB](https://github.com/microsoft/documentdb)
extension for MongoDB-like
queries (MIT licensed). Works perfectly. Note that this is not the same
product as Amazon
- DocumentDB. Last tested 2025-04 with the FerretDB distribution 2.1.0.
+ DocumentDB. Last tested 2025-07 with the FerretDB distribution 2.3.1.
- The [Hydra Columnar](https://github.com/hydradatabase/columnar) extension
for column-oriented
storage and parallel queries (Apache license). Works perfectly (last tested
2025-05 with v1.1.2).
@@ -119,7 +119,7 @@ The following PostgreSQL-compatible databases have been
tested:
- The [RisingWave](https://github.com/risingwavelabs/risingwave) event
streaming database (Apache
license) is mostly working. It does not support `GENERATED ALWAYS AS
IDENTITY` or `SERIAL`
- columns, nor `VACUUM ANALYZE`. Last tested 2025-06 with v2.4.2.
+ columns, nor `VACUUM ANALYZE`. Last tested 2025-07 with v2.4.3.
- The [CrateDB](https://crate.io/) distributed database (Apache licence).
CrateDB does not support
rows (e.g. `SELECT (1,2)`), does not support the `time`, `varbit`, `bytea`,
`jsonb` and `hstore`
@@ -127,14 +127,24 @@ The following PostgreSQL-compatible databases have been
tested:
PostgreSQL functions such as `factorial`, does not return a correct type OID
for text columns in
rows returned from a prepared statement, doesn't support Unicode
identifiers, doesn't support the
`COPY` protocol, doesn't support `TRUNCATE TABLE`. It works with these
limitations with pg-el
- (last tested 2025-06 with version 5.10.9).
+ (last tested 2025-07 with version 5.10.10).
- The [CockroachDB](https://github.com/cockroachdb/cockroach) distributed
database (source-available
but non-free software licence). Note that this database does not implement
the large object
functionality, and its interpretation of SQL occasionally differs from that
of PostgreSQL.
Currently fails with an internal error on the SQL generated by our query for
`pg-table-owner`, and
fails on the boolean vector syntax b'1001000'. Works with these limitations
with pg-el (last
- tested 2025-06 with CockroachDB CCL v25.2).
+ tested 2025-07 with CockroachDB CCL v25.2).
+
+- The [YDB by Yandex](https://ydb.tech/docs/en/postgresql/docker-connect)
distributed database
+ (Apache licence). Has very limited PostgreSQL compatibility. For example, an
empty query string
+ leads to a hung connection, and the `bit` type is returned as a string with
the wrong oid. Last
+ tested 2025-05 with version 23-4.
+
+- The [Materialize](https://materialize.com/) operational database (a
proprietary differential
+ dataflow database) has many limitations in its PostgreSQL compatibility: no
support for primary
+ keys, unique constraints, check constraints, for the `bit` type for example.
It works with these
+ limitations with pg-el (last tested 2025-07 with Materialize v0.149).
- The [QuestDB](https://questdb.io/) time series database (Apache licensed)
has very limited
PostgreSQL support, and does not support the `integer` type for example.
Last tested 2025-06 with
@@ -147,16 +157,6 @@ The following PostgreSQL-compatible databases have been
tested:
recognize basic PostgreSQL types such as `INT2`. It also does not for
example support the `CHR`
and `MD5` functions, row expressions, and `WHERE` clauses without a `FROM`
clause.
-- The [YDB by Yandex](https://ydb.tech/docs/en/postgresql/docker-connect)
distributed database
- (Apache licence). Has very limited PostgreSQL compatibility. For example, an
empty query string
- leads to a hung connection, and the `bit` type is returned as a string with
the wrong oid. Last
- tested 2025-05 with version 23-4.
-
-- The [Materialize](https://materialize.com/) operational database (a
proprietary differential
- dataflow database) has many limitations in its PostgreSQL compatibility: no
support for primary
- keys, unique constraints, check constraints, for the 'bit' type for example.
It works with these
- limitations with pg-el (last tested 2025-06 with Materialize v0.146).
-
- [YottaDB Octo](https://gitlab.com/YottaDB/DBMS/YDBOcto), which is built on
the YottaDB key-value
store (which is historically based on the MUMPS programming language). GNU
AGPL v3 licence. There
are many limitations in the PostgreSQL compatibility: no user
metainformation, no cursors, no
