This release is based on PostgreSQL 9.6.12 and Postgres Pro Standard 126.96.36.199. All improvements inherited from PostgreSQL 9.6.12 are listed in PostgreSQL 9.6.12 Release Notes.
Major enhancements over Postgres Pro Standard 188.8.131.52 include:
Changed the default authentication method for installations on SUSE Linux Enterprise Server systems, as well as Red Hat Enterprise Linux 7 and its derivatives. Now local connections use the
peermethod, while network connections use
md5. For details on supported authentication methods, see Section 19.3.
Backported the patch that addresses
dsm_attach()race condition when DSM handles are reused; in vanilla PostgreSQL, this fix is targeted for the future updates only. The patch is hoped to resolve issues when the server reports the following error message:
ERROR: dsa_area could not attach to segment.
Changed delivery model for pg_probackup utility:
On Linux, pg_probackup is now provided in the
pg-probackup-std-9.6package. On ALT Linux and Debian-based systems, when upgrading from Postgres Pro Standard 184.108.40.206 or lower, run
apt-get dist-upgrade) to ensure that all new dependencies are handled correctly.
On Windows, pg_probackup now has a separate installer. You have to install core components of the current Postgres Pro version before installing pg_probackup.
Added new options to Postgres Pro interactive installer for Windows. Now you can:
libcas the default collation provider. Previously, Postgres Pro Standard always used
Select a Windows user that starts Postgres Pro service. By default, Postgres Pro service is started on behalf of
Fixed amcheck to eliminate false-positive reports of invalid index structure, which were manifested by the following error message:
ERROR: heap tuple lacks matching index tuple within index.
Fixed performance degradation for index-only scans over wide indexes.
Ended support for ALT Linux SPT 6.0 and Windows 7 SP1.
bloomindexes are now tracked correctly by pg_probackup in the
pg_pathmanmodule to version 1.5.5. As compared to version 1.5.2 provided in the previous Postgres Pro releases, the following enhancements were introduced:
pg_pathmanupgrade scripts to avoid issues caused by a different the number of
pg_pathman1.4 and 1.5 major versions.
Trying to call
pg_pathmanfunctions when this extension is disabled does not cause server failures anymore; now an error is raised instead.
Different partitioning strategies can now be successfully applied to the same table.
pg_variablesmodule to version 1.2. As compared to the version provided in the previous Postgres Pro releases, the following enhancements were introduced:
Added support for array types.
Improved module stability.
Changed empty package handling. An empty package is now removed only after the transaction that emptied it has ended.
(See Section F.44.)
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.
Since pg_probackup delivery model changed in Postgres Pro Standard 18.104.22.168, 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 22.214.171.124 or lower, you must call the
REINDEX command for indexes that used
If you are upgrading from Postgres Pro Standard 126.96.36.199 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 188.8.131.52, as well as rename the
pgpro_build function to
pgpro_source_id. If you are upgrading your Postgres Pro installation from a binary package, the
pgpro_upgrade script is run automatically, unless you are prompted to run it 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.
If you have compiled Postgres Pro from source code or created your database in a non-default location, you must run the
pgpro_upgrade script manually.
On RPM-based Linux distributions, if you are upgrading from version 184.108.40.206 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.