E.8. Postgres Pro Standard 184.108.40.206
Release date: 2019-08-12
This release is based on PostgreSQL 9.6.15 and Postgres Pro Standard 220.127.116.11. All improvements inherited from PostgreSQL 9.6.15 are listed in PostgreSQL 9.6.15 Release Notes.
Major enhancements over Postgres Pro Standard 18.104.22.168 include:
Added support for Debian 10.
Improved planning accuracy for queries with
ORclauses. Now sorting is performed correctly for such queries.
Fixed implementation of greater than (>) and not equal to (<>) operators for the
E.8.2. Migration to Version 22.214.171.124
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 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.