E.20. Postgres Pro Standard 188.8.131.52
Release date: 2017-11-14
This release is based on PostgreSQL 9.6.6 and Postgres Pro Standard 184.108.40.206. All improvements inherited from PostgreSQL 9.6.6 are listed in PostgreSQL 9.6.6 Release Notes.
Major enhancements over Postgres Pro Standard 220.127.116.11 include:
Improved cache invalidation mechanisms.
COPY (SELECT * FROMinstead.
INSTEAD OFtriggers on views selected from partitioned tables.
ALTER TABLEnow also renames auto naming sequences.
Disabled some dangerous optimizations for
SELECT ... FOR SHARE/UPDATEon PostgreSQL 9.5.
Improved error handling in concurrent partitioning background worker.
Prohibited execution of queries
UPDATEif such queries touch more than one partition of
Fixed a bug causing crashes on
WHEREconditions that point to gaps between partitions.
Restored compatibility with pg_repack.
For the full list of changes, see pg_pathman Wiki.
Updated the pg_probackup utility from version 2.0.2 to 2.0.11, which includes the following new features:
Password prompt interruption is now handled correctly.
The provided passwords are checked to be is non-empty.
The files that have not changed since the previous backup are not included into the next incremental backup.
Database version is now added into backup meta information.
Other miscellaneous bug fixes.
E.20.2. Migration to Version 18.104.22.168
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. If you are upgrading from Postgres Pro Standard 22.214.171.124, it is enough to install the new version into your current installation directory. When 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. 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, perform a dump/restore using pg_dumpall.