Docs 769-b (#6505)

jpe442 · web-flow · commit 8ca9efcf294a · 2025-02-26T16:15:45.000-05:00
* Small fixes for new upgrade command.

* Updates for 5.7

* Added a note about upgrading both PGD version and Postgres major version simultaneously with pgd node upgrade.

* small changes

* Added a note about upgrading to older versions than 5.7.0 of PGD and using bdr_pg_upgrade instead.

* updated upgrade paths to include 4.37 to 5.7.0

* Small changes

* Took reconcile with TPA bit out as it no longer works.

* added redirect

* Fixed redirect and changed filename.

* Small changes in language to show you can upgrade both major versions of PGD and Postgres.

* Small changes in index.

* Some link fixes.

* some small changes
diff --git a/product_docs/docs/pgd/5.6/upgrades/upgrade_paths.mdx b/product_docs/docs/pgd/5.6/upgrades/upgrade_paths.mdx
@@ -27,6 +27,7 @@ release before upgrading to the latest version 5 release. After upgrading to
 | 4.3.2 | 5.1.0 or later |
 | 4.3.3 | 5.1.0 or later |
 
+
 ## Upgrading from version 3.7 to version 5
 
 Starting with version 3.7.23, you can upgrade directly to version 5.3.0 or later. 
diff --git a/product_docs/docs/pgd/5.7/rel_notes/pgd_5.7.0_rel_notes.mdx b/product_docs/docs/pgd/5.7/rel_notes/pgd_5.7.0_rel_notes.mdx
@@ -26,7 +26,7 @@ guarantees that every transaction is decoded and sent at least once.</p>
 </details></td><td></td></tr>
 <tr><td>PGD CLI</td><td>5.7.0</td><td><details><summary>Added a new local assesment feature for local non-PGD nodes to the CLI</summary><hr/><p>The new feature allows you to assess the local node for compatibility with PGD. The feature is available as <code>pgd assess</code>. Full details are available in <a href="/pgd/latest/cli/command_ref">the CLI command reference</a>.</p>
 </details></td><td></td></tr>
-<tr><td>PGD CLI</td><td>5.7.0</td><td><details><summary>Added <code>pgd node upgrade</code> functionality to the PGD CLI.</summary><hr/><p>The new command allows you to upgrade a node to the latest version of PGD and Postgres. It integrates the operation of <code>bdr_pg_upgrade</code> into the CLI and is run locally. See <a href="/pgd/latest/cli/command_ref/node/upgrade">pgd node upgrade</a> and <a href="/pgd/latest/upgrades/bdr_pg_upgrade">inplace upgrades</a> for more information.</p>
+<tr><td>PGD CLI</td><td>5.7.0</td><td><details><summary>Added <code>pgd node upgrade</code> functionality to the PGD CLI.</summary><hr/><p>The new command allows you to upgrade a node to the latest version of PGD and Postgres. It integrates the operation of <code>bdr_pg_upgrade</code> into the CLI and is run locally. See <a href="/pgd/latest/cli/command_ref/node/upgrade">pgd node upgrade</a> and <a href="/pgd/latest/upgrades/inplace_upgrade">inplace upgrades</a> for more information.</p>
 </details></td><td></td></tr>
 <tr><td>BDR</td><td>5.7.0</td><td><details><summary>Fixed an issue whereby concurrent joins of subscriber-only nodes occasionally stopped responding.</summary><hr/><p>A node could end up waiting for the local state of another concurrently joined node to advance, which caused the system to stop responding.</p>
 </details></td><td>42964</td></tr>
diff --git a/product_docs/docs/pgd/5.7/rel_notes/src/relnote_5.7.0.yml b/product_docs/docs/pgd/5.7/rel_notes/src/relnote_5.7.0.yml
@@ -239,7 +239,7 @@ relnotes:
 - relnote: Added `pgd node upgrade` functionality to the PGD CLI.
   component: PGD CLI
   details: |
-    The new command allows you to upgrade a node to the latest version of PGD and Postgres. It integrates the operation of `bdr_pg_upgrade` into the CLI and is run locally. See [pgd node upgrade](/pgd/latest/cli/command_ref/node/upgrade) and [inplace upgrades](/pgd/latest/upgrades/bdr_pg_upgrade) for more information.
+    The new command allows you to upgrade a node to the latest version of PGD and Postgres. It integrates the operation of `bdr_pg_upgrade` into the CLI and is run locally. See [pgd node upgrade](/pgd/latest/cli/command_ref/node/upgrade) and [inplace upgrades](/pgd/latest/upgrades/inplace_upgrade) for more information.
   jira: ""
   addresses: ""
   type: Feature
diff --git a/product_docs/docs/pgd/5.7/upgrades/index.mdx b/product_docs/docs/pgd/5.7/upgrades/index.mdx
@@ -25,11 +25,11 @@ EDB Postgres Distributed is a flexible platform. This means that your upgrade pa
 * **[Compatibility changes](compatibility)** &mdash; 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
+## Upgrading Postgres or Postgres and PGD major versions
 
-* **[In-place Postgres upgrades](bdr_pg_upgrade)** &mdash; How to use `pgd node upgrade` to manually upgrade the Postgres version on a node, or nodes.
+* **[In-place Postgres major version upgrades](inplace_upgrade)** &mdash; How to use `pgd node upgrade` to manually upgrade the Postgres version or Postgres and PGD major version on a node, or nodes.
 
-* **[Rolling major version upgrades](upgrading_major_rolling)** &mdash; How to perform a major version upgrade of Postgres on a cluster deployed using TPA.
+* **[Rolling major version upgrades](upgrading_major_rolling)** &mdash; How to perform a major version upgrade of Postgres on a cluster.
 
 
 ## Other upgrades
diff --git a/product_docs/docs/pgd/5.7/upgrades/inplace_upgrade.mdx b/product_docs/docs/pgd/5.7/upgrades/inplace_upgrade.mdx
@@ -1,8 +1,15 @@
 ---
-title: In-place Postgres major version upgrades
+title: In-place Postgres or Postgres and PGD major version upgrades
+redirects:
+  - pgd/latest/upgrades/bdr_pg_upgrade/
 ---
 
-You can upgrade a PGD node to a newer major version of Postgres using the command-line utility [pgd node upgrade](/pgd/latest/cli/command_ref/node/upgrade.mdx).
+You can upgrade a PGD node to a newer major version of Postgres or a major version of Postgres and PGD using the command-line utility [pgd node upgrade](/pgd/5.7/cli/command_ref/node/upgrade.mdx).
+
+!!!Note
+In previous versions before 5.7.0, the command used for in-place major version upgrades was `bdr_pg_upgrade`. 
+However, this command did not have an option to upgrade both Postgres major versions and PGD versions simultaneously, as `pgd node upgrade` does.
+!!!
 
 `pgd node upgrade` is a wrapper around the standard [pg_upgrade](https://www.postgresql.org/docs/current/pgupgrade.html) that
 adds PGD-specific logic to the process to ensure a smooth upgrade.
@@ -40,13 +47,18 @@ You must meet several prerequisites for `pgd node upgrade`:
     match the old cluster configuration.
 - Databases, tables, and other objects must not exist in the new cluster.
 
+!!! Note
+When upgrading to PGD 5.7.0+, you do not need to have both cluster run the same PGD version. 
+The new cluster must be running 5.7.0+. 
+In that case `pgd node upgrade` will upgrade both the PGD version to 5.7.x as well as upgrading the Postgres major version.
+!!!
 
 We also recommend having the old Postgres cluster up prior to running `pgd node upgrade`.
 The CLI starts the old Postgres cluster if it's shut down.
 
 ## Usage
 
-To upgrade to a newer major version of Postgres, you must first install the new version.
+To upgrade to a newer major version of Postgres or Postgres and PGD, you must first install the new version packages.
 
 ### `pgd node upgrade` command-line
 
diff --git a/product_docs/docs/pgd/5.7/upgrades/manual_overview.mdx b/product_docs/docs/pgd/5.7/upgrades/manual_overview.mdx
@@ -191,8 +191,8 @@ version of Postgres you're upgrading to.
 
 Upgrading to a new major version of Postgres is more complicated than upgrading to a minor version.
 
-EDB Postgres Distributed provides a bdr_pg_upgrade command line utility,
-which you can use to do [in-place Postgres major version upgrades](bdr_pg_upgrade).
+EDB Postgres Distributed provides a pgd node upgrade command line utility,
+which you can use to do [in-place Postgres major version upgrades](inplace_upgrade).
 
 !!! Note
     When upgrading to a new major version of any software, including Postgres, the
diff --git a/product_docs/docs/pgd/5.7/upgrades/tpa_overview.mdx b/product_docs/docs/pgd/5.7/upgrades/tpa_overview.mdx
@@ -5,7 +5,7 @@ title: Upgrading PGD clusters with TPA
 !!! Note No Postgres major version upgrades
 TPA doesn't currently support major version upgrades of Postgres. 
 
-To perform a major version upgrade of Postgres, see [In-place Postgres major version upgrades](bdr_pg_upgrade).
+To perform a major version upgrade of Postgres, see [In-place Postgres major version upgrades](inplace_upgrade).
 !!!
 
 If you used TPA to install your cluster, you can also use TPA to upgrade it. The techniques outlined here can perform minor and major version upgrades of the PGD software. They can also perform minor version upgrades of Postgres. 
diff --git a/product_docs/docs/pgd/5.7/upgrades/upgrade_paths.mdx b/product_docs/docs/pgd/5.7/upgrades/upgrade_paths.mdx
@@ -26,6 +26,7 @@ release before upgrading to the latest version 5 release. After upgrading to
 | 4.3.1 | 5.1.0 or later |
 | 4.3.2 | 5.1.0 or later |
 | 4.3.3 | 5.1.0 or later |
+| 4.3.7 | 5.7.0 or later |
 
 ## Upgrading from version 3.7 to version 5
 
diff --git a/product_docs/docs/pgd/5.7/upgrades/upgrading_major_rolling.mdx b/product_docs/docs/pgd/5.7/upgrades/upgrading_major_rolling.mdx
diff --git a/product_docs/docs/tpa/23/reference/reconciling-local-changes.mdx b/product_docs/docs/tpa/23/reference/reconciling-local-changes.mdx
