Choosing a Postgres distribution v5
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 which Postgres distribution is used. Therefore, it is essential to adopt the Postgres distribution best suited to your business needs. For example, if having the feature "Commit At Most Once (CAMO)" is mission critical to your use case, you should not adopt open source PostgreSQL because it does not 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 |
| Asynchronous replication | 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+ |
| Distribured 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 |
| Transparent Data Encryption | N | 15+ | 15+ |
| 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+ |
| Transaction Streaming | 14+ | 13+ | 14+ |
| Lag Tracker | N | Y | 14+ |
| Assessment Tooling | 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+ |