branch: elpa/pg
commit 1ce69d58f195ec01f0139dc8b442366c381c30c3
Author: Eric Marsden <eric.mars...@risk-engineering.org>
Commit: Eric Marsden <eric.mars...@risk-engineering.org>

    Update information on tested versions of PostgreSQL variants
---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 5febecb1d2..725d70388e 100644
--- a/README.md
+++ b/README.md
@@ -124,7 +124,7 @@ The following PostgreSQL-compatible databases or extensions 
have been tested:
   though the `pg_sequences` table is not implemented so certain tests fail. 
YugabyteDB does not have
   full compatibility with PostgreSQL SQL, and for example `GENERATED ALWAYS 
AS` columns are not
   supported, and `LISTEN` and `NOTIFY` are not supported. It does support 
certain extensions such as
-  pgvector, however. Last tested on 2025-05 against version 2.25.
+  pgvector, however. Last tested on 2025-07 against version 2.25.
 
 - 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`
@@ -153,7 +153,7 @@ The following PostgreSQL-compatible databases or extensions 
have been tested:
 - 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.151).
+  limitations with pg-el (last tested 2025-07 with Materialize v0.152).
 
 - 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

Reply via email to