E.9. Postgres Pro Standard 220.127.116.11
Release date: 2019-07-03
This release is based on PostgreSQL 9.6.14 and Postgres Pro Standard 18.104.22.168. All improvements inherited from PostgreSQL 9.6.14 are listed in PostgreSQL 9.6.14 Release Notes.
Major enhancements over Postgres Pro Standard 22.214.171.124 include:
pg_probackupmodule to version 2.1.3. As compared with version 2.0.26, it offers the following major improvements:
Backup and restore of a remote Postgres Pro instance via SSH.
Merging incremental backups with their expired parent backups to satisfy retention policy.
Backing up files and directories located outside of Postgres Pro data directory, such as configuration or log files.
checkdbcommand for validating all data files in the Postgres Pro instance and logical verification of indexes using amcheck.
For a full list of changes, see pg_probackup Wiki.
pg_pathmanmodule to version 1.5.8. As compared to version 1.5.5 provided in the previous Postgres Pro releases, the following enhancements were introduced:
Fixed handling of tables with multilevel partitioning. Previously,
SELECT FOR SHAREand
SELECT FOR UPDATEcommands for such tables could return the following error:
ERROR: variable not found in subplan target lists.
E.9.2. Migration to Version 126.96.36.199
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 188.8.131.52, 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 184.108.40.206 or lower, you must call the
REINDEX command for indexes that used
If you are upgrading from Postgres Pro Standard 220.127.116.11 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 18.104.22.168, 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 22.214.171.124 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.