E.13. Postgres Pro Standard 18.104.22.168
Release date: 2018-10-11
This release is based on Postgres Pro Standard 22.214.171.124 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 the online_analyze module, so that now it forbids nested
Increased the number of partitions of the shared buffer mapping hash table to 1024, which can improve performance on multi-core systems.
amcheckmodule that allows you to verify logical consistency of the structure of indexes. (See amcheck 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
Updated pg_probackup to version 2.0.21, which provides the following bug fixes:
Issues related to restoring backups taken on standbys are resolved.
log-rotation-ageparameters are now parsed correctly.
showcommand now dynamically changes width of the displayed output to improve readability for large tables.
restorecommand now correctly restores all symbolic links to tablespaces.
If checksums are enabled, the
validatecommand now verifies checksums for blocks.
E.13.2. Migration to Version 126.96.36.199
Depending on your current installation, the upgrade procedure will differ.
To upgrade from a Postgres Pro Standard version based on any previous PostgreSQL major release, make sure you have installed its latest minor version, and then perform a dump/restore using pg_dumpall or use the pg_upgrade utility.
To upgrade from a Postgres Pro Standard version based on the same PostgreSQL major release, a dump/restore is not required.
When upgrading from versions 188.8.131.52 or lower, you must call the
REINDEX command for indexes that used
If you are upgrading from Postgres Pro Standard 184.108.40.206 or lower, you must also use the pgpro_upgrade script provided in this distribution. This script updates metadata information to handle catalog number format change introduced after Postgres Pro Standard 220.127.116.11, as well as rename the
pgpro_build function to
pgpro_source_id. If you are upgrading your Postgres Pro installation from a binary package, the
pgpro_upgrade script is run automatically, unless you are prompted to run it manually.
If you run
pgpro_upgrade manually, you must stop postgres service. The script must be run on behalf of the user owning the database (typically postgres). Running
pgpro_upgrade as root will result in an error. For details, see pgpro_upgrade.
If you have compiled Postgres Pro from source code or created your database in a non-default location, you must run the
pgpro_upgrade script manually.
On RPM-based Linux distributions, if you are upgrading from version 18.104.22.168 or lower, make sure to move the data directory from
pgsql to the
pgpro directory before running the
To migrate from vanilla PostgreSQL 9.6.x, perform a dump/restore using pg_dumpall.