E.16. Postgres Pro Standard 9.6.10.3
Release date: 2018-10-11
E.16.1. Overview
This release is based onPostgres Pro Standard 9.6.10.2 and provides the following improvements:
Added a fix for incorrect calculation of the minimum recovery point on standby servers, which could cause incorrect page references.
Updated theonline_analyze module, so that now it forbids nested
ANALYZEcalls.Increased the number of partitions of the shared buffer mapping hash table to 1024, which can improve performance on multi-core systems.
Added
amcheckmodule that allows you to verify logical consistency of the structure of indexes. (Seeamcheck for details.)Fixed backup restore on a master server to avoid race conditions when applying two-phase transactions.
For Windows systems, fixed an issue with reloading dictionaries provided by the
shared_ispellmodule.Updatedpg_probackup to version 2.0.21, which provides the following bug fixes:
Issues related to restoring backups taken on standbys are resolved.
The
log-rotation-sizeandlog-rotation-ageparameters are now parsed correctly.The
showcommand now dynamically changes width of the displayed output to improve readability for large tables.The
restorecommand now correctly restores all symbolic links to tablespaces.If checksums are enabled, the
validatecommand now verifies checksums for blocks.
E.16.2. Migration to Version 9.6.10.3
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.
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, perform a dump/restore usingpg_dumpall.