This release is based on PostgreSQL 9.6.16 and Postgres Pro Standard 22.214.171.124. All improvements inherited from PostgreSQL 9.6.16 are listed in PostgreSQL 9.6.16 Release Notes.
Major enhancements over Postgres Pro Standard 126.96.36.199 include:
Ended support for SLES 12. If you would like to use Postgres Pro on this operating system, install Postgres Pro Standard 10 or higher.
Ended support for Ubuntu 18.10.
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.
Updated the mamonsu module to version 2.4.1. You can now convert all system and Postgres Pro metrics definitions provided by mamonsu to the format supported by the native Zabbix agent.
Upgraded pgbouncer to version 1.11.0.
Upgraded pg_probackup to version 2.2.5.
Migration to Version 188.8.131.52
Depending on your current installation, the upgrade procedure will differ.
To upgrade from a Postgres Pro Standard version based on any previous PostgreSQL major release, make sure you have installed its latest minor version, and then perform a dump/restore using pg_dumpall or use the pg_upgrade utility.
To upgrade from a Postgres Pro Standard version based on the same PostgreSQL major release, a dump/restore is not required.
Since pg_probackup delivery model changed in Postgres Pro Standard 184.108.40.206, when upgrading from a lower version on ALT Linux and Debian-based systems, run
apt dist-upgrade (or
apt-get dist-upgrade) to ensure that all new dependencies are handled correctly. On Windows, you have to run a separate pg_probackup installer to complete the upgrade.
When upgrading from versions 220.127.116.11 or lower, you must call the
REINDEX command for indexes that used
If you are upgrading from Postgres Pro Standard 18.104.22.168 or lower, you must also use the pgpro_upgrade script provided in this distribution. This script updates metadata information to handle catalog number format change introduced after Postgres Pro Standard 22.214.171.124, as well as rename the
pgpro_build function to
pgpro_upgrade script is usually run automatically. However, if you have created your database in a non-default location, you must run the
pgpro_upgrade script manually.
If you run
pgpro_upgrade manually, you must stop 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.
On RPM-based Linux distributions, if you are upgrading from version 126.96.36.199 or lower, make sure to move the data directory from
pgsql to the
pgpro directory before running the
To migrate from vanilla PostgreSQL 9.6.x, make sure you have installed its latest available minor version and then perform a dump/restore using pg_dumpall.