From d10d956727ed9709e9a7ac902f09082dd71c2a2c Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Wed, 6 Sep 2023 13:32:40 -0400 Subject: [PATCH] Edits to upgrading text --- .../docs/pgd/4/upgrades/upgrade_paths.mdx | 8 ++++---- .../docs/pgd/5/upgrades/upgrade_paths.mdx | 20 ++++++++++--------- 2 files changed, 15 insertions(+), 13 deletions(-) diff --git a/product_docs/docs/pgd/4/upgrades/upgrade_paths.mdx b/product_docs/docs/pgd/4/upgrades/upgrade_paths.mdx index 5d682abe58e..7c222c72fc9 100644 --- a/product_docs/docs/pgd/4/upgrades/upgrade_paths.mdx +++ b/product_docs/docs/pgd/4/upgrades/upgrade_paths.mdx @@ -4,13 +4,13 @@ title: Supported BDR upgrade paths ## Upgrading within version 4 -Beginning with version 4, EDB Postgres Distributed has adopted [semantic versioning](https://semver.org/). All changes within the same major version will be backward compatible, lowering the risk when upgrading and allowing you to choose any later minor or patch release as the upgrade target. You can upgrade from any version 4.x release to a later 4.x release. +Beginning with version 4, EDB Postgres Distributed adopted [semantic versioning](https://semver.org/). All changes within the same major version are backward compatible, lowering the risk when upgrading and allowing you to choose any later minor or patch release as the upgrade target. You can upgrade from any version 4.x release to a later 4.x release. ## Upgrading from version 3.7 to version 4 -Generally, we recommend you upgrade to the latest version 3.7 release, before -upgrading to the latest version 4 release. You will have to be using 3.7.15 or later +Generally, we recommend that you upgrade to the latest version 3.7 release before +upgrading to the latest version 4 release. You must be using 3.7.15 or later before upgrading to 4. See [Upgrading within from 3.7](/pgd/3.7/bdr/upgrades/supported_paths/#upgrading-within-version-37) in the 3.7 documentation for more information. After upgrading to 3.7.15 or later, the following upgrade paths are possible. @@ -28,4 +28,4 @@ following upgrade paths are possible. ## Upgrading from version 3.6 to version 4 -Currently there are no direct upgrade paths from 3.6 to 4. You must first upgrade your cluster to 3.7 before upgrading to 4. See [Upgrading from 3.6](/pgd/3.7/bdr/upgrades/supported_paths/#upgrading-from-version-36) in the 3.7 documentation for more information. \ No newline at end of file +Currently, there are no direct upgrade paths from 3.6 to 4. You must first upgrade your cluster to 3.7 before upgrading to 4. See [Upgrading from 3.6](/pgd/3.7/bdr/upgrades/supported_paths/#upgrading-from-version-36) in the 3.7 documentation for more information. \ No newline at end of file diff --git a/product_docs/docs/pgd/5/upgrades/upgrade_paths.mdx b/product_docs/docs/pgd/5/upgrades/upgrade_paths.mdx index d911ba899e3..20de151f4dc 100644 --- a/product_docs/docs/pgd/5/upgrades/upgrade_paths.mdx +++ b/product_docs/docs/pgd/5/upgrades/upgrade_paths.mdx @@ -8,11 +8,13 @@ You can upgrade from any version 5.x release to a later 5.x release. ## Upgrading from version 4 to version 5 -Upgrades from PGD 4 to PGD 5 are supported from version 4.3.0. For older +Upgrades from PGD 4 to PGD 5 are supported from version 4.3.0. For earlier versions, upgrade to 4.3.0 before upgrading to 5. See [Upgrading within 4](/pgd/4/upgrades/upgrade_paths/#upgrading-within-version-4) for more -information. Generally, we recommend you upgrade to the latest version 4 -release, before upgrading to the latest version 5 release. After upgrading to +information. + +Generally, we recommend that you upgrade to the latest version 4 +release before upgrading to the latest version 5 release. After upgrading to 4.3.0 or later, the following upgrade paths are possible. | From version | To version | @@ -23,18 +25,18 @@ release, before upgrading to the latest version 5 release. After upgrading to ## Upgrading from version 3.7 to version 5 -At this time, TPA has only enabled upgrades from PGD 3.7 to 4 and PGD 4 to 5. -Customers moving from 3.7 to 5 and desiring automation would need to use this -two-step upgrade path and will potentially have their proxy architecture changed +At this time, TPA has enabled upgrades only from PGD 3.7 to 4 and PGD 4 to 5. +If you're moving from 3.7 to 5 and want automation, you need to use this +two-step upgrade path. Potentially, your proxy architecture will change multiple times from HA Proxy to HARP and finally to PGD Proxy. -Significant development has been done to make upgrading directly from 3.7 to 5 +Significant development was done to make upgrading directly from 3.7 to 5 possible and easier. We've expanded the database versions supported with PGD 5 and enabled the upgradeability of the BDR extension across multiple PGD -versions. Previously, we only supported upgrades from the previous major +versions. Previously, we supported upgrades only from the previous major version. Often, a database upgrade was also required because only one database major version was supported by both PGD versions. Development is currently ongoing to provide a direct upgrade path from 3.7 to 5 -using TPA by Q4. In the interim, customers may reach out to EDB Professional +using TPA by Q4. In the interim, you can reach out to EDB Professional Services or Support for assistance and guidance. \ No newline at end of file