E.23. Postgres Pro Standard 9.6.6.1
Release date: 2017-11-14
E.23.1. Overview
This release is based onPostgreSQL 9.6.6 andPostgres Pro Standard 9.6.5.1. All improvements inherited fromPostgreSQL 9.6.6 are listed inPostgreSQL 9.6.6 Release Notes.
Major enhancements overPostgres Pro Standard 9.6.5.1 include:
Updatedpg_pathman module to version 1.4.8. (Seepg_pathman andSection F.36.1.1.) As compared to version 1.4.3, the following enhancements were introduced:
Improved cache invalidation mechanisms.
Disabled
COPYcommand. Usepartitioned_tableTOCOPY (SELECT * FROMinstead.partitioned_table) TOFixed
INSTEAD OFtriggers on views selected from partitioned tables.ALTER TABLEnow also renames auto naming sequences.partitioned_tableRENAME TODisabled some dangerous optimizations for
SELECT ... FOR SHARE/UPDATEonPostgreSQL 9.5.Improved error handling in concurrent partitioning background worker.
Prohibited execution of queries
DELETE FROMandpartitioned_table_1USINGpartitioned_table_2...UPDATEif such queries touch more than one partition ofpartitioned_table_1FROMpartitioned_table_2...partitioned_table_1.Fixed a bug causing crashes on
RESET ALL.Fixed
WHEREconditions that point to gaps between partitions.Restored compatibility withpg_repack.
For the full list of changes, seepg_pathman Wiki.
Updated thepg_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.23.2. Migration to Version 9.6.6.1
Depending on your current installation, the upgrade procedure will differ.
To upgrade from aPostgres Pro Standard version based on any previousPostgreSQL major release, make sure you have installed its latest minor version, and then perform a dump/restore usingpg_dumpall or use thepg_upgrade utility.
To upgrade from aPostgres Pro Standard version based on the samePostgreSQL major release, a dump/restore is not required. If you are upgrading fromPostgres Pro Standard 9.6.5.1, it is enough to install the new version into your current installation directory. When upgrading fromPostgres Pro Standard 9.6.4.1 or lower, you must also use thepgpro_upgrade script provided in this distribution. This script updates metadata information to handle catalog number format change introduced afterPostgres Pro Standard 9.6.4.1. If you are upgrading yourPostgres Pro installation from a binary package, thepgpro_upgrade script is run automatically, unless you are prompted to run it manually.
Important
If you runpgpro_upgrade manually, you must stop postgres service. The script must be run on behalf of the user owning the database (typically postgres). Runningpgpro_upgrade as root will result in an error. For details, seepgpro_upgrade.
If you have compiledPostgres Pro from source code or created your database in a non-default location, you must run thepgpro_upgrade script manually.
Note
On RPM-based Linux distributions, if you are upgrading from version 9.6.2.1 or lower, make sure to move the data directory frompgsql to thepgpro directory before running thepgpro_upgrade script.
To migrate from vanilla PostgreSQL 9.6.x, perform a dump/restore usingpg_dumpall.