Deployment options
The following table shows the deployment options supported for each Postgres distribution.
| PostgreSQL | EDB Postgres Extended Server | EDB Postgres Advanced Server | EDB Postgres Advanced Server in Oracle compatibility mode | |
|---|---|---|---|---|
| EDB Postgres AI Cloud Service (*) | Yes | Yes (**) | Yes | Yes |
| EDB CloudNativePG Global Cluster | No | Yes | Yes | Yes |
| EDB CloudNativePG Cluster | Yes | Yes | Yes | Yes |
| TPA | Yes | Yes | Yes | Yes |
| Manual installation on virtual machines or physical servers: EPAS, PGE and PostgreSQL | Yes | Yes | Yes | Yes |
Note
(*) You can monitor external databases in the EDB Postgres AI Console using the EDB Postgres AI Agent.
(**) EDB Postgres AI Cloud Service supports EDB Postgres Extended Server only in combination with EDB Postgres Distributed.
Deployment options for reliability and availability
High availability and fault tolerance are available with EDB databases when deployed together with EDB Postgres Distributed.
| PostgreSQL | EDB Postgres Extended Server | EDB Postgres Advanced Server | EDB Postgres Advanced Server in Oracle compatibility mode | |
|---|---|---|---|---|
| Single instance | Yes | Yes | Yes | Yes |
| Primary/secondary replication | Yes | Yes | Yes | Yes |
| PGD - Distributed high availability | Yes (*) | Yes | Yes | Yes |
Note
(*) EDB Postgres Distributed (PGD) only supports a limited set of PostgreSQL features. Refer to PGD - Choosing a Postgres distribution for more information.
Single instance
Single instance databases are great for development and testing, but for production workloads, you need to consider high availability and fault tolerance.
Primary/secondary replication
Primary/Secondary replication is a common high availability solution for databases. In this configuration, a primary database server is responsible for processing read and write requests. A secondary database server is setup to replicate the primary database server. If the primary database server fails, the secondary database server can take over and become the primary database server.
This configuration provides fault tolerance and high availability in a particular location. This is available with EDB Postgres® Advanced Server (EPAS) and EDB Postgres Extended Server (PGE).
Distributed high availability
High availability is a critical requirement for mission-critical workloads. EDB Postgres Distributed (PGD) provides a distributed database environment designed to ensure high availability and fault tolerance for mission-critical workloads. PGD can use EPAS, PGE, or PostgreSQL databases as the underlying replicated database. PGD is available for self-managed deployment and on the EDB Postgres AI Cloud Service (as the Distributed High Availability option).
Could this page be better? Report a problem or suggest an addition!