Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Edits to upgrading text #4776

Merged
merged 2 commits into from
Oct 12, 2023
Merged

Edits to upgrading text #4776

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d10d956
Edits to upgrading text
ebgitelman Sep 6, 2023
c562e85
Merge branch 'develop' into docs/edits_to_pgd_pr4766
djw-m Oct 12, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions product_docs/docs/pgd/4/upgrades/upgrade_paths.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand All @@ -28,4 +28,5 @@ 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.
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.

12 changes: 7 additions & 5 deletions product_docs/docs/pgd/5/upgrades/upgrade_paths.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 |
Expand All @@ -26,8 +28,8 @@ release, before upgrading to the latest version 5 release. After upgrading to

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. Using this process, it's possible your proxy architecture will change
multiple times: from HA Proxy to HARP and then to PGD Proxy.
two-step upgrade path. Potentially, your proxy architecture will change
multiple times from HA Proxy to HARP and finally to PGD Proxy.

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
Expand Down