E.9. Postgres Pro Standard 9.6.16.1
Release date: 2019-11-27
E.9.1. Overview
This release is based onPostgreSQL 9.6.16 andPostgres Pro Standard 9.6.15.2. All improvements inherited fromPostgreSQL 9.6.16 are listed inPostgreSQL 9.6.16 Release Notes.
Major enhancements overPostgres Pro Standard 9.6.15.2 include:
Ended support for SLES 12. If you would like to usePostgres Pro on this operating system, installPostgres Pro Standard 10 or higher.
Ended support for Ubuntu 18.10.
Forbade access to tables that belong to partition hierarchies in which bothpg_pathman and standardPostgreSQL inheritance have been used for partitioning. Mixing different partitioning mechanisms in a single table hierarchy is unsupported and should have never been attempted. Previously, you could get duplicated query results from such table hierarchies.
Updated themamonsu module to version 2.4.1. You can now convert all system andPostgres Pro metrics definitions provided bymamonsu to the format supported by the nativeZabbix agent.
Upgradedpgbouncer to version 1.11.0.
Upgradedpg_probackup to version 2.2.5.
E.9.2. Migration to Version 9.6.16.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. Thepgpro_upgrade script is usually run automatically. However, if you have created your database in a non-default location, you must run thepgpro_upgrade script 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.
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.