branch: elpa/pg
commit 0ed5bb3a7bf9dfa2addcc43ab01df7cfc9a4dbb8
Author: Eric Marsden <eric.mars...@risk-engineering.org>
Commit: Eric Marsden <eric.mars...@risk-engineering.org>
Add information on compatibility with the CedarDB database
---
README.md | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/README.md b/README.md
index 98b378484f9..229789857f2 100644
--- a/README.md
+++ b/README.md
@@ -124,11 +124,11 @@ 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-07 against version 2.25.
+ pgvector, however. Last tested on 2025-08 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`
- columns, nor `VACUUM ANALYZE`. Last tested 2025-07 with v2.5.0.
+ columns, nor `VACUUM ANALYZE`. Last tested 2025-08 with v2.5.1.
- 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`
@@ -143,7 +143,7 @@ The following PostgreSQL-compatible databases or extensions
have been tested:
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-07 with CockroachDB CCL v25.2).
+ tested 2025-08 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
@@ -153,7 +153,11 @@ 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.152).
+ limitations with pg-el (last tested 2025-08 with Materialize v0.153).
+
+- 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-08 with CedarDB version v2025-08-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-06 with
