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.

- \*\* :ref:`Upgrading PGD clusters manually <Upgrading PGD clusters manually>`  \*\* — If you manually installed and configured
  your PGD cluster, you can move a cluster between versions, both minor
  and major.

- \*\* :ref:`Supported PGD upgrade paths <Supported PGD upgrade paths>`  \*\* — Several supported upgrade paths are
  available.

- \*\* :ref:`PGD compatibility <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
-----------------------------------------------------

- \*\* :ref:`In-place Postgres major version upgrades <pgd node upgrade>`  \*\* — How to use ``pgd node upgrade`` to manually
  upgrade the Postgres version or Postgres and PGD major version on one
  or more nodes.

- \*\* :ref:`Performing a Postgres major version rolling upgrade on a PGD cluster <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
--------------

- \*\* :ref:`Application schema upgrades <Application schema upgrades>`  \*\* — A guide for safely upgrading your
  application’s schema when running multiple distributed servers with
  PGD.

.. toctree::
  :maxdepth: 3

  upgrades--manual_overview
  upgrades--upgrade_paths
  upgrades--compatibility
  upgrades--app_upgrades
  upgrades--inplace_upgrade
  upgrades--upgrading_major_rolling