branch: elpa/pg
commit c1e0471784d8234b7dd4e072a177a36ef5564fef
Author: Eric Marsden <[email protected]>
Commit: Eric Marsden <[email protected]>
Update information on latest tested versions for PostgreSQL variants
---
README.md | 22 ++++++++++++----------
1 file changed, 12 insertions(+), 10 deletions(-)
diff --git a/README.md b/README.md
index a733950b75d..70a36c3a2cb 100644
--- a/README.md
+++ b/README.md
@@ -72,10 +72,10 @@ The following PostgreSQL-compatible databases or extensions
have been tested:
extension rather than a distinct database implementation).
- [IvorySQL](https://www.ivorysql.org/) works perfectly (this Apache licensed
fork of PostgreSQL
- adds some features for compatibility with Oracle). Last tested 2025-08 with
version 4.5.
+ adds some features for compatibility with Oracle). Last tested 2025-12 with
version 5.0.
- The [Timescale DB](https://www.timescale.com/) extension for time series
data, source available
- but non open source. This works perfectly (last tested 2025-09 with version
2.21).
+ but non open source. This works perfectly (last tested 2025-12 with version
2.24).
- The [CitusDB](https://github.com/citusdata/citus) extension for sharding
PostgreSQL over multiple
hosts (AGPLv3 licence). Works perfectly (last tested 2025-07 with Citus
version 13.0).
@@ -131,7 +131,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-11 with v2.6.2.
+ columns, nor `VACUUM ANALYZE`. Last tested 2025-12 with v2.6.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`
@@ -139,14 +139,14 @@ 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.1.1).
+ (last tested 2025-12 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
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-11 with CockroachDB CCL v25.4).
+ tested 2025-12 with CockroachDB CCL v25.4).
- 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
@@ -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-24.
+ 2025-12 with CedarDB version v2025-12-02.
- 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
@@ -198,7 +198,7 @@ The following PostgreSQL-compatible databases or extensions
have been tested:
`pg_catalog.pg_types` table are not the same as those used by PostgreSQL
(e.g. `Int64` instead of
`int8`), so our parsing machinery does not work. This database also has more
restrictions on the
use of identifiers than PostgreSQL (for example, `id` is not accepted as a
column name, nor are
- identifiers containing Unicode characters). Last tested v1.0.0-beta1 in
2025-11.
+ identifiers containing Unicode characters). Last tested v1.0.0-beta2 in
2025-12.
- Hosted PostgreSQL services that have been tested: as of 2025-06 render.com
is running a Debian
build of PostgreSQL 16.8 and works fine (requires TLS connection), as of
2024-12
@@ -210,9 +210,11 @@ The following PostgreSQL-compatible databases or
extensions have been tested:
Data works fine. As of 2025-11, the free tier of Supabase works fine (you
will probably have to
increase the read timeout using the `read_timeout` URL parameter).
-- Untested but likely to work: Amazon RDS, Google Cloud SQL, Azure Database
for PostgreSQL, Amazon
- Aurora, CrunchyData Warehouse. You may however encounter difficulties with
TLS connections, as
- noted above. Reports on success or problems encountered with these databases
are welcome.
+- Untested but likely to work: different [PostgreSQL-derived
+ forks](https://wiki.postgresql.org/wiki/PostgreSQL_derived_databases), such
as Amazon RDS, Google
+ Cloud SQL, Azure Database for PostgreSQL, Amazon Aurora, CrunchyData
Warehouse. You may however
+ encounter difficulties with TLS connections, as noted above. Reports on
success or problems
+ encountered with these databases are welcome.
PostgreSQL variants or proxies that **don't work** with pg-el:
