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 with TPA ** — If you installed using TPA, you can use its automated upgrade feature to upgrade to the latest minor versions.

• ** 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 by PostgreSQL version ** — 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

• ** In-place Postgres major version upgrades ** — How to use bdr_pg_upgrade to manually upgrade the Postgres version on a node, or nodes.

• ** Performing a Postgres major version rolling upgrade on a PGD cluster built with TPA ** — How to perform a major version upgrade of Postgres on a cluster deployed using TPA.

Other upgrades

• ** Application schema upgrades ** — A guide for safely upgrading your application’s schema when running multiple distributed servers with PGD.

• Upgrading PGD clusters with TPA
  • Minor and major PGD upgrades
  • Prerequisites
  • Upgrading
  • TPA’s automated rolling upgrade procedure
    • TPA upgrades - step by step
• Upgrading PGD clusters manually
  • Upgrade planning
    • Rolling upgrade considerations
    • Rolling server software upgrades
    • Rolling upgrade using node join
    • Upgrading a CAMO-enabled cluster
  • Upgrade preparation
  • Server software upgrade
    • BDR extension upgrade
    • Stop Postgres
    • Upgrade packages
    • Start Postgres
    • Postgres upgrade
    • Minor version Postgres upgrade
    • Major version Postgres upgrade
  • Upgrade check and validation
  • Moving from HARP to PGD Proxy
• Supported PGD upgrade paths
  • Upgrading within version 5
  • Upgrading from version 4 to version 5
  • Upgrading from version 3.7 to version 5
• Compatibility changes
  • Connection routing
  • Commit At Most Once
  • Eager All-Node Replication
  • Lag Control
  • Catalogs
• In-place Postgres major version upgrades
  • Terminology
  • Precautions
  • Usage
    • bdr_pg_upgrade command-line
    • Synopsis
    • Options
    • Environment variables
    • Example
    • Steps performed
    • PGD Postgres checks
    • pg_upgrade steps
    • PGD post-upgrade steps
• Application schema upgrades
  • Rolling application schema upgrades
• Performing a Postgres major version rolling upgrade on a PGD cluster built with TPA
  • Upgrading Postgres major versions
    • Prepare the upgrade
    • Perform the upgrade on each node
    • Reconcile the upgrade with TPA
  • Worked example
    • Confirm the current Postgres version
    • Verify that the target node isn’t the write leader
    • Perform a planned switchover
    • Stop Postgres on the target node
    • Install PGD and utilities
    • Initialize the new Postgres instance
    • Migrate configuration to the new Postgres version
    • Verify the Postgres service is inactive
    • Swap PGDATA directories for version upgrade
    • Update the Postgres service configuration
    • Restart Postgres
    • Validate the new Postgres version
    • Clean up post-upgrade
    • Next steps
    • Check Postgres versions across the cluster
    • Reconcile with TPA