Upgrade PGD and Postgres independently, or move both to a new major version at the same time. They're closely related but distinct products, each with its own upgrade path.
Before upgrading
Supported PGD upgrade paths — Learn which source versions can upgrade directly to this release, whether you're upgrading PGD alone or upgrading Postgres and PGD together, and regardless of how your cluster is deployed.
Compatibility changes — Review the behavior and configuration differences before upgrading an existing 4.x or 5.x cluster, whether you're upgrading PGD alone or upgrading Postgres and PGD together, and regardless of how your cluster is deployed.
PGD compatibility with Postgres versions — Confirm your target Postgres major version, operating system, and architecture are supported before picking a target PGD version.
Planning your upgrade — Review rolling versus full-downtime upgrades and the general plan/prepare/upgrade/validate process, regardless of what you're upgrading or how your cluster is deployed.
Choosing your upgrade type
Upgrading PGD — Move a cluster to a new PGD version, minor or major, without necessarily changing your Postgres version.
Upgrading Postgres — Move to a new Postgres version, minor or major, without necessarily changing your PGD version.
Upgrading Postgres and PGD together — Perform a combined Postgres and PGD major-version upgrade.
Upgrading your application schema — Apply DDL changes across a live cluster one node at a time, using rolling application schema upgrades and conflict resolver configuration, independent of the PGD or Postgres version you're running.
Upgrading with other deployment methods — If your cluster is deployed with Trusted Postgres Architect (TPA), EDB Postgres Distributed for Kubernetes, or Hybrid Manager, that tool manages the upgrade for you instead of the manual, CLI-driven steps described above.