Choosing a Postgres distribution v5.6
EDB Postgres Distributed can be deployed with three different Postgres distributions: PostgreSQL, EDB Postgres Extended Server, or EDB Postgres Advanced Server. The availability of particular EDB Postgres Distributed features depends on the Postgres distribution being used. Therefore, it's essential to adopt the Postgres distribution best suited to your business needs. For example, if having the Commit At Most Once (CAMO) feature is mission critical to your use case, don't adopt open source PostgreSQL, which doesn't have the core capabilities required to handle CAMO.
The following table lists features of EDB Postgres Distributed that are dependent on the Postgres distribution and version.
| Feature | PostgreSQL | EDB Postgres Extended | EDB Postgres Advanced |
|---|---|---|---|
| Rolling application and database upgrades | Y | Y | Y |
| Row-level last-update wins conflict resolution | Y | Y | Y |
| DDL replication | Y | Y | Y |
| Granular DDL Locking | Y | Y | Y |
| Streaming of large transactions | v14+ | v13+ | v14+ |
| Distributed sequences | Y | Y | Y |
| Subscribe-only nodes | Y | Y | Y |
| Monitoring | Y | Y | Y |
| OpenTelemetry support | Y | Y | Y |
| Parallel apply | Y | Y | Y |
| Conflict-free replicated data types (CRDTs) | Y | Y | Y |
| Column-level conflict resolution | Y | Y | Y |
| Transform triggers | Y | Y | Y |
| Conflict triggers | Y | Y | Y |
| Asynchronous replication | Y | Y | Y |
| Legacy synchronous replication | Y | Y | Y |
| Group Commit | N | Y | 14+ |
| Commit At Most Once (CAMO) | N | Y | 14+ |
| Eager Conflict Resolution | N | Y | 14+ |
| Lag Control | N | Y | 14+ |
| Decoding Worker | N | 13+ | 14+ |
| Lag tracker | N | Y | 14+ |
| Missing partition conflict | N | Y | 14+ |
| No need for UPDATE Trigger on tables with TOAST | N | Y | 14+ |
| Automatically hold back FREEZE | N | Y | 14+ |
| Transparent Data Encryption | N | 15+ | 15+ |