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

-  \*\* :ref:`Upgrading 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:`Compatibility changes <Compatibility changes>`  \*\* — 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
------------------

-  \*\* :ref:`In-place Postgres upgrades <In-place Postgres major version upgrades>`  \*\* — How to use ``bdr_pg_upgrade`` to manually
   upgrade the Postgres version on a node, or nodes.

-  \*\* :ref:`Rolling major version upgrades <upgrading_major_rolling>`  \*\* — How to perform a major version upgrade of
   Postgres on a cluster deployed using TPA.

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

  Administration--upgrades--tpa_overview
  Administration--upgrades--manual_overview
  Administration--upgrades--upgrade_paths
  Administration--upgrades--compatibility
  Administration--upgrades--bdr_pg_upgrade
  Administration--upgrades--app_upgrades