Deploying PGD 4 manually v4

EDB offers automated PGD deployment using Trusted Postgres Architect (TPA) because it's generally more reliable than manual processes. Consult Deploying with TPA for full details on how to install TPA and use its automated best-practice-driven PGD deployment options.

To complement automated installation, and to enable alternative installation and deployment processes, this section of the documentation looks at the basic operations needed to manually configure a three-node PGD 4 cluster (with a local subgroup) and PGD CLI.

This section includes, for completeness, instructions for installing PostgreSQL. If you're familiar with that, then skip to step 3 in the linked sections that follow.

Each step is outlined and followed by a worked example with further detail. This documentation is not a quick start but an exploration of PGD installation. It shows how to configure a basic deployment that will be used for additional examples of PGD administration tasks.

Note

Installation of HARP proxies is not covered in this guide. For information on how to install HARP proxies, see the HARP Proxy Installation Guide.

The examples deploy a 3-node cluster of EDB Postgres Advanced Server 14 on Red Hat Enterprise Linux 9. These instructions also apply to RHEL derivatives like Alma Linux, Rocky Linux, or Oracle Linux.

At the highest level, manually deploying PGD involves the following steps:

   1: Provisioning and configuring hosts to run the cluster on.

   2: Installing your selected Postgres version on each of the hosts.

   3: Configuring repositories to install PGD to add PGD capabilities to each host.

   4: Initializing Postgres and installing PGD software on each host.

   5: Connecting the cluster by connecting to each node and telling it to join the cluster.

   6: Checking the cluster by running SQL commands and confirming replication has happened.

   7: Using PGD CLI covers installing PGD CLI and how to use it to inspect and manage your cluster.