Deploying manually v5

EDB offers automated PGD deployment using TPA (Trusted Postgres Architect) because its generally more reliable than manual processes. Consult Deploying with TPA for how to install TPA and use its automated best-practice driven PGD deployment options for full details. Or refer to any of the Quickstart walkthroughs which use TPA to get you up and running quickly.

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 cluster (with a local sub-group), PGD Proxy and PGD CLI.

This guide includes, for completeness, how to install PostgreSQL. If you are familiar with that, then skip to step 3.

Each step will be outlined and followed by a worked example with further detail. This guide is not a quickstart guide, but an exploration of PGD installation, and it will configure a basic deployment which we will be using for further examples of PGD administration tasks.

In the examples, we will be deploying a 3-node cluster of EDB Postgres Advanced Server 16 on Red Hat Enterprise Linux 9. These instructions should 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: Check the cluster by running SQL commands and confirming replication has happened.

   7: Configuring proxies by creating a proxy config file.

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