E.12. Postgres Pro Standard 9.6.14.1
Release date: 2019-07-03
E.12.1. Overview
This release is based onPostgreSQL 9.6.14 andPostgres Pro Standard 9.6.13.1. All improvements inherited fromPostgreSQL 9.6.14 are listed inPostgreSQL 9.6.14 Release Notes.
Major enhancements overPostgres Pro Standard 9.6.13.1 include:
Updated
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 remotePostgres Pro instance via SSH.
Merging incremental backups with their expired parent backups to satisfy retention policy.
Backing up files and directories located outside ofPostgres Pro data directory, such as configuration or log files.
The
checkdbcommand for validating all data files in thePostgres Pro instance and logical verification of indexes usingamcheck.
For a full list of changes, seepg_probackup Wiki.
Updated
pg_pathmanmodule to version 1.5.8. As compared to version 1.5.5 provided in the previousPostgres Pro releases, the following enhancements were introduced:Fixed handling of tables with multilevel partitioning. Previously,
SELECT FOR SHAREandSELECT FOR UPDATEcommands for such tables could return the following error:ERROR: variable not found in subplan target lists.Enhanced
pg_pathmanstability.
E.12.2. Migration to Version 9.6.14.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.
Sincepg_probackup delivery model changed inPostgres Pro Standard 9.6.12.1, when upgrading from a lower version on ALT Linux and Debian-based systems, runapt dist-upgrade (orapt-get dist-upgrade) to ensure that all new dependencies are handled correctly. On Windows, you have to run a separatepg_probackup installer to complete the upgrade.
When upgrading from versions 9.6.8.2 or lower, you must call theREINDEX command for indexes that usedmchar ormvarchar types.
If you are upgrading fromPostgres Pro Standard 9.6.7.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, as well as rename thepgpro_build function topgpro_source_id. 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.
Note
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, make sure you have installed its latest available minor version and then perform a dump/restore usingpg_dumpall.