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

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

diff --git a/README.md b/README.md
index 74aa814a4cd..a733950b75d 100644
--- a/README.md
+++ b/README.md
@@ -139,7 +139,7 @@ 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-11 with version 6.0.3).
+  (last tested 2025-11 with version 6.1.1).
 
 - 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
@@ -160,7 +160,7 @@ The following PostgreSQL-compatible databases or extensions 
have been tested:
 
 - 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-11 with CedarDB version v2025-11-06.
+  2025-11 with CedarDB version v2025-11-24.
 
 - 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-10 with

Reply via email to