This release is based on PostgreSQL 9.6.17 and Postgres Pro Standard 188.8.131.52. All improvements inherited from PostgreSQL 9.6.17 are listed in PostgreSQL 9.6.17 Release Notes.
Major enhancements over Postgres Pro Standard 184.108.40.206 include:
Increased the maximum value of the track_activity_query_size parameter to 1MB. In vanilla PostgreSQL, this change is targeted for version 13.
Improved query performance with row-level security policy enabled by correctly marking numeric comparison functions as leakproof.
Fixed planner's optimization to correctly take into account similar
ORclauses if they reference columns that are different, but have the same position in different indexes.
mcharextension to correctly handle the
SIMILAR TOregular expressions.
Upgraded pg_probackup to version 2.2.7.
Upgraded mamonsu to version 2.4.4.
Migration to Version 220.127.116.11
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.
numeric_le are actually leakproof, they were not marked as such in Postgres Pro Standard 18.104.22.168 or lower, which could lead to incorrect query optimization. In particular, it negatively affected query execution if row-level security policy was in use. Version 22.214.171.124 repairs this issue for new installations by correcting the initial catalog data, but existing installations will still have incorrect markings unless you update
pg_proc entries for these functions. You can run pg_upgrade to upgrade your server instance to a version containing the corrected initial data, or manually correct these entries in each database of the installation using the
ALTER FUNCTION command. For example:
ALTER FUNCTION pg_catalog.numeric_eq VOLATILE
Since pg_probackup delivery model changed in Postgres Pro Standard 126.96.36.199, 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 188.8.131.52 or lower, you must call the
REINDEX command for indexes that used
If you are upgrading from Postgres Pro Standard 184.108.40.206 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 220.127.116.11, 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 18.104.22.168 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.