Note
This section covers manually installed or CLI-driven clusters. If your cluster is deployed with Trusted Postgres Architect (TPA), EDB Postgres Distributed for Kubernetes, or Hybrid Manager, see Upgrading with other deployment methods instead.
Move both Postgres and PGD to a new version at the same time, minor or major.
Performing a combined minor upgrade
Moving both Postgres and PGD to a new minor version at the same time means upgrading each node in
place rather than replacing it:
installing the new PGD packages built for your Postgres version also picks up the latest available Postgres
minor version for it, so a single package install and restart covers both. No new data directory,
pg_upgrade, or node join is needed, since neither a PGD nor a Postgres minor version upgrade changes the
on-disk format.
See Performing a combined minor upgrade for the complete procedure.
Performing a combined major upgrade
Moving both Postgres and PGD to a new major version at the same time uses the same pgd node
upgrade tool as a Postgres-only major upgrade, since
pgd node upgrade only ever migrates the Postgres version. The only difference is which packages you
install: install the combined package built for both new major versions together (for example,
edb-pgd6-expanded-pg17 to move to PGD 6 on Postgres 17) instead of a Postgres-only package. PGD itself
upgrades to the new version automatically once the new binaries detect the older version installed.
Because moving to a new major PGD version also means moving off HARP Proxy or PGD Proxy, the complete procedure, covering full-downtime, rolling in-place, and replace-node paths, is on a dedicated page for each source version:
- Upgrading PGD 4 and Postgres to PGD 6 — for a PGD 4.4.1 cluster using HARP Proxy.
- Upgrading PGD 5 and Postgres to PGD 6 — for a PGD 5.9 cluster using PGD Proxy.
For either source version, how a newly joined PGD 6 node interacts with routing and leader election while the rest of the cluster is still on the old version hasn't been confirmed for the replace-node path. Verify with EDB Support or engineering before relying on it.
If you're not also changing your PGD version, see Upgrading Postgres instead.