Supported BDR upgrade paths v4
Upgrading within version 4
Beginning with version 4, EDB Postgres Distributed adopted semantic versioning. 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.
Due to interdependencies between EDB Postgres Distributed and EDB Postgres Advanced Server or EDB Postgres Extended, there are occasions when it is important to always upgrade both components at once. More detailed compatibility information can be found below.
| PGD version | EPAS version | PGE version |
|---|---|---|
| Up to 4.3.0 | Up to 14.7 / 15.2 | Up to 14.9 / 15.4 |
| 4.3.1, 4.3.2 | 14.8, 14.9 / 15.3, 15.4 | Up to 14.9/ 15.4 |
| 4.3.3 and higher | 14.10 / 15.5 and higher | 14.10 / 15.5 and higher |
This dependency is bidirectional dependency.
- Upgrading your Postgres servers will require you to upgrade your PGD installation to the relevant version.
- Upgrading your PGD installation will require you to upgrade your Postgres servers to the relevant version.
Upgrading from version 3.7 to version 4
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 in the 3.7 documentation for more information. After upgrading to 3.7.15 or later, the following upgrade paths are possible.
| From version | To versions (range) |
|---|---|
| 3.7.15 | 4.0.2 to 4.2.1 |
| 3.7.16 | 4.0.2 to 4.2.1 |
| 3.7.17 | 4.2.0 to 4.2.1 |
| 3.7.18 | 4.2.1 only |
| 3.7.19 | 4.2.2 only |
| 3.7.20 | 4.3.0 to 4.3.2 |
| 3.7.21 | 4.3.1 to 4.3.2 |
| 3.7.22 | 4.3.2 only |
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 in the 3.7 documentation for more information.