branch: elpa/pg
commit 959d6fcc853794547c9f219e919fcc73ece107fc
Author: Eric Marsden <[email protected]>
Commit: Eric Marsden <[email protected]>

    Update information on tested variant versions
---
 README.md | 19 ++++++++++---------
 1 file changed, 10 insertions(+), 9 deletions(-)

diff --git a/README.md b/README.md
index d76b6f2a671..ba995dc5f86 100644
--- a/README.md
+++ b/README.md
@@ -66,7 +66,7 @@ The following PostgreSQL-compatible databases or extensions 
have been tested:
 
 - [Neon](https://neon.tech/) “serverless PostgreSQL” works perfectly. This is 
a commercially hosted
   service using a new storage engine for PostgreSQL, that they make available 
under the Apache
-  licence. Last tested 2025-08.
+  licence. Last tested 2025-10.
 
 - [ParadeDB](https://www.paradedb.com/) version 0.13.1 works perfectly (it's 
really a PostgreSQL
   extension rather than a distinct database implementation).
@@ -81,7 +81,7 @@ The following PostgreSQL-compatible databases or extensions 
have been tested:
   hosts (AGPLv3 licence). Works perfectly (last tested 2025-07 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-07
+  designed for better multithreading and solid state storage, works perfectly. 
Last tested 2025-10
   with version beta12.
 
 - The [Microsoft DocumentDB](https://github.com/microsoft/documentdb) 
extension for MongoDB-like
@@ -115,7 +115,7 @@ The following PostgreSQL-compatible databases or extensions 
have been tested:
 
 - [PolarDB for PostgreSQL](https://github.com/ApsaraDB/PolarDB-for-PostgreSQL) 
is free software
   (Apache 2 licence) developed by Alibaba Cloud, also available as a 
commercial hosted service with
-  a proprietary distributed storage architecture. It works perfectly with 
pg-el (last tested 2025-09
+  a proprietary distributed storage architecture. It works perfectly with 
pg-el (last tested 2025-10
   with version 15.14).
 
 - [openGauss](https://opengauss.org/en/) is an open source (Mulan PSL v2) fork 
of PostgreSQL
@@ -124,6 +124,7 @@ The following PostgreSQL-compatible databases or extensions 
have been tested:
 - [Xata](https://xata.io/) “serverless PostgreSQL” has many limitations 
including lack of support
   for `CREATE DATABASE`, `CREATE COLLATION`, for XML processing, for temporary 
tables, for cursors,
   for `EXPLAIN`, for `CREATE EXTENSION`, for `DROP FUNCTION`, for functions 
such as `pg_notify`.
+  Last tested 2025-10 with a version that reports itself as 15.12.
 
 - The [YugabyteDB](https://yugabyte.com/) distributed database (Apache 
licence). Mostly working
   though the `pg_sequences` table is not implemented so certain tests fail. 
YugabyteDB does not have
@@ -133,7 +134,7 @@ The following PostgreSQL-compatible databases or extensions 
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-09 with v2.6.0.
+  columns, nor `VACUUM ANALYZE`. Last tested 2025-10 with v2.6.0.
 
 - 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`
@@ -141,28 +142,28 @@ The following PostgreSQL-compatible databases or 
extensions 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-09 with version 5.10.12).
+  (last tested 2025-10 with version 6.0.2).
 
 - 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-09 with CockroachDB CCL v25.3).
+  tested 2025-10 with CockroachDB CCL v25.3).
 
 - 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.
+  tested 2025-10 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-09 with Materialize v0.158).
+  limitations with pg-el (last tested 2025-10 with Materialize v0.159).
 
 - The [CedarDB](https://cedardb.com/) database spun off from the Umbra 
research database developed
   at the University of Munich is fairly PostgreSQL compatible and works well 
with pg-el. Last tested
-  2025-09 with CedarDB version v2025-09-24.
+  2025-10 with CedarDB version v2025-10-07.
 
 - 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-09 with

Reply via email to