Upgrading#
While PGD and Postgres are closely related, they’re separate products with separate upgrade paths. This section covers how to upgrade both PGD and Postgres.
Upgrading PGD#
EDB Postgres Distributed is a flexible platform. This means that your upgrade path depends largely on how you installed PGD.
** Upgrading PGD clusters manually ** — If you manually installed and configured your PGD cluster, you can move a cluster between versions, both minor and major.
** Supported PGD upgrade paths ** — Several supported upgrade paths are available.
** PGD compatibility ** — If you’re upgrading from PGD 3.x or 4.x to PGD 5.x or later, you need to understand the compatibility changes between versions.
Upgrading Postgres or Postgres and PGD major versions#
** In-place Postgres major version upgrades ** — How to use
pgd node upgradeto manually upgrade the Postgres version or Postgres and PGD major version on one or more nodes.** Performing a Postgres major version rolling upgrade on a PGD cluster ** — How to perform a major version upgrade of Postgres on a cluster.
Other upgrades#
** Application schema upgrades ** — A guide for safely upgrading your application’s schema when running multiple distributed servers with PGD.
- Upgrading PGD clusters manually
- Supported PGD upgrade paths
- Compatibility changes
- Application schema upgrades
- In-place Postgres or Postgres and PGD major version upgrades
- Performing a Postgres major version rolling upgrade on a PGD cluster
- Upgrading Postgres major versions
- Worked example: Upgrade PGD 4 to PGD 6.1
- Overview
- Confirm the harp-proxy leader
- Fence the node
- Stop the Postgres service
- Stop HARP manager
- Remove and install packages
- Start the Postgres service
- Start HARP manager
- Unfence the node
- Repeat steps for all nodes
- Confirm cluster version
- Confirm SCRAM hashes
- Enable routing
- Switch to Connection Manager
- Stop harp manager and proxy services.
- Worked example: Upgrade PGD 5 to PGD 6.1
- Prerequisites
- Pre-upgrade steps
- Post-upgrade steps