E.3. Postgres Pro Standard 22.214.171.124
Release date: 2020-08-21
This release is based on PostgreSQL 9.6.19 and Postgres Pro Standard 126.96.36.199. All improvements inherited from PostgreSQL 9.6.19 are listed in PostgreSQL 9.6.19 Release Notes.
Major enhancements over Postgres Pro Standard 188.8.131.52 include:
Upgraded pg_probackup to latest version 2.4.2:
New options and flags can now be used to add flexibility to
Incremental restore and support for multi-timeline incremental chains have been added.
Postgres Pro parameters
primary_conninfocan be used during restore.
archive-getcommands considerably reworked.
Improvements have been achieved in speed and memory consumption.
See pg_probackup documentation for details.
Upgraded mamonsu for Linux systems to version 2.5.1. Now it is based on Python 3. Version 2.3.4 is still provided for Windows systems.
Ended support for ALT Linux 7, while support for ALT Linux SPT 7 is retained for convenience of existing customers.
Ended support for SUSE Linux Enterprise Server 11.
Fixed race conditions in BRIN index that caused errors:
"failed to find parent tuple for heap-only tuple ...".
The error could occur when the
brin_summarize_new_values()function and HOT updates were executed simultaneously in concurrent transactions.
"corrupted BRIN index: inconsistent range map".
The error could occur when BRIN index's desummarization and a bitmap scan were executed simultaneously in concurrent transactions.
E.3.2. Migration to Version 184.108.40.206
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.
numeric_le are actually leakproof, they were not marked as such in Postgres Pro Standard 220.127.116.11 or lower, which could lead to incorrect query optimization. In particular, it negatively affected query execution if row-level security policy was in use. Version 18.104.22.168 repairs this issue for new installations by correcting the initial catalog data, but existing installations will still have incorrect markings unless you update
pg_proc entries for these functions. You can run pg_upgrade to upgrade your server instance to a version containing the corrected initial data, or manually correct these entries in each database of the installation using the
ALTER FUNCTION command. For example:
ALTER FUNCTION pg_catalog.numeric_eq LEAKPROOF
Since pg_probackup delivery model changed in Postgres Pro Standard 22.214.171.124, when upgrading from a lower version on ALT Linux and Debian-based systems, run
apt dist-upgrade (or
apt-get dist-upgrade) to ensure that all new dependencies are handled correctly. On Windows, you have to run a separate pg_probackup installer to complete the upgrade.
When upgrading from versions 126.96.36.199 or lower, you must call the
REINDEX command for indexes that used
If you are upgrading from Postgres Pro Standard 188.8.131.52 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 184.108.40.206, as well as rename the
pgpro_build function to
pgpro_upgrade script is usually run automatically. However, if you have created your database in a non-default location, you must run the
pgpro_upgrade script 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.
On RPM-based Linux distributions, if you are upgrading from version 220.127.116.11 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, make sure you have installed its latest available minor version and then perform a dump/restore using pg_dumpall.