E.20. Postgres Pro Standard 9.6.8.2
Release date: 2018-03-20
E.20.1. Overview
This release is based onPostgreSQL 9.6.8 andPostgres Pro Standard 9.6.8.1. All improvements inherited fromPostgreSQL 9.6.8 are listed inPostgreSQL 9.6.8 Release Notes.
Major enhancements overPostgres Pro Standard 9.6.8.1 include:
Updated thepg_probackup utility from version 2.0.11 to 2.0.16, which includes the following new features:
Fixed an infinite loop that could happen during page validation.
Fixed segfault for the case of parallel
PTRACKconnections.Allowed to use the
delete-waloption withoutdelete-expired.Fixed CVE-2018-1058. Schema name is now explicitly used on every function call.
You can now use
pgpro_buildfunction to get the latest commit ID for the source files of the current release.Fixed an issue with sort ordering of some Russian letters in the
mcharmodule. UseREINDEX DATABASEcommand to update indexes.
E.20.2. Migration to Version 9.6.8.2
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.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.
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.