Multi-Region Cluster

PostgreSQL Multi-Region Cluster

PostgreSQL Multi-Region Cluster is a pre-packaged solution that automatically creates a highly available PostgreSQL database cluster across multiple platform regions using platform-managed stack templates.

Database Cluster Topology

The PostgreSQL Multi-Region Cluster package uses the officially supported PostgreSQL Primary-Secondary topology and adds one more Secondary node for disaster recovery. As a result, the final database topology is:

PrimaryThe main PostgreSQL server.
SecondaryReplicated PostgreSQL server in another region.
Secondary for DRAn additional Secondary node used for disaster recovery.
PostgreSQL multi-region cluster topology
PostgreSQL Multi-Region Cluster uses a Primary-Secondary-Secondary topology.

The package also includes a highly available Pgpool-II Load Balancer layer. Pgpool-II distributes requests and manages the PostgreSQL replication topology.

Data-center-level availability

The combination of PostgreSQL replication and highly available Pgpool-II nodes provides out-of-the-box high availability and failover, so the database remains accessible even if one region becomes unavailable.

Cluster Installation

1

Find PostgreSQL Multi-Region Cluster

Open the platform Marketplace and find PostgreSQL Multi-Region Cluster in the Clusters section or through the Search field.

PostgreSQL Multi-Region Cluster in Marketplace
Find the PostgreSQL Multi-Region Cluster package in Marketplace.
2

Configure the installation

In the installation window, specify:

  • Version — select the preferred PostgreSQL version.
  • Environment — provide a name for grouping the database cluster environments.
  • Create separate environment group — enable this option when the environment group should be isolated.
  • PostgreSQL Regions — choose the regions where database cluster environments will be deployed.
  • Pgpool-II enabled — enable this option to place Pgpool-II load-balancing, monitoring, and management nodes in front of the database nodes.
  • Pgpool regions — select the regions where Pgpool-II nodes should be deployed.
!

Region order matters

The first PostgreSQL region selected during installation becomes the Primary server region. All other selected PostgreSQL regions become Secondary server regions.

Install PostgreSQL Multi-Region Cluster
Configure the PostgreSQL version, environment group, database regions, and Pgpool-II regions.

Click Install when the settings are ready.

3

Wait for cluster installation

Installation can take several minutes. After completion, the platform displays a success window and sends emails containing the appropriate information, including entry-point details and access credentials.

Environment Grouping

To view all environments related to the PostgreSQL multi-region cluster together, switch to the environment group specified during installation. The source example uses pgcluster.

PostgreSQL cluster environment group
Switch to the configured environment group to view all cluster-related environments.

Cluster Entry Point

The default entry point for the multi-region cluster is the leader Pgpool-II node, which is deployed in the first region.

If the leader Pgpool-II node fails, use any other Pgpool-II node through its hostname or IP address.

PostgreSQL multi-region cluster environments
The leader Pgpool-II node is the default entry point, while other Pgpool-II nodes can be used as alternatives.

Automatic client-side failover

If the database client supports multiple entry points, configure all Pgpool-II entry points in the connection string so the client can automatically switch when one becomes unavailable.

Expected Result

A PostgreSQL cluster is deployed across multiple platform regions using a Primary-Secondary-Secondary topology with a highly available Pgpool-II layer. The first selected PostgreSQL region hosts the Primary server, the other PostgreSQL regions host Secondary servers, and the leader Pgpool-II node acts as the default database entry point.

Important Notes

  • The PostgreSQL Multi-Region Cluster package uses a Primary-Secondary-Secondary topology.
  • The additional Secondary node is intended for disaster recovery.
  • The first selected PostgreSQL region becomes the Primary server region.
  • All other selected PostgreSQL regions become Secondary server regions.
  • Pgpool-II can be enabled for load balancing, monitoring, and topology management.
  • The leader Pgpool-II node in the first region is the default cluster entry point.
  • If the leader Pgpool-II node fails, another Pgpool-II hostname or IP can be used.
  • Clients that support multiple entry points can configure all of them for automatic failover.