This release is based on PostgreSQL 9.5.20 and Postgres Pro Standard 126.96.36.199. All improvements inherited from PostgreSQL 9.5.20 are listed in PostgreSQL 9.5.20 Release Notes.
As compared to Postgres Pro Standard 188.8.131.52, this release includes the following enhancement:
Forbade access to tables that belong to partition hierarchies in which both pg_pathman and standard PostgreSQL inheritance have been used for partitioning. Mixing different partitioning mechanisms in a single table hierarchy is unsupported and should have never been attempted. Previously, you could get duplicated query results from such table hierarchies.
Migration to Version 184.108.40.206
Depending on your current installation, the upgrade procedure will differ.
If you are running Postgres Pro Standard version 220.127.116.11 or higher, it is enough to install the 18.104.22.168 version into the same directory. However, if you are upgrading from PostgreSQL 9.5.x or lower versions of Postgres Pro Standard, some catalog changes should be applied, so pgpro_upgrade script is required to complete the upgrade:
If your database is in the default location,
pgpro_upgradeis run automatically, unless you are prompted to run it manually.
If you created your database in a non-default location, you must run
pgpro_upgrade manually, you must stop the
postgres service. The script must be run on behalf of the user owning the database (typically postgres). Running
pgpro_upgrade as root will result in an error. For details, see pgpro_upgrade.
To migrate to this version from vanilla PostgreSQL 9.5.4 or lower, perform a dump/restore using pg_dumpall.