This release is based on PostgreSQL 11.9 and Postgres Pro Standard 11.8.1. All improvements inherited from PostgreSQL 11.9 are listed in PostgreSQL 11.9 Release Notes.
Major enhancements over Postgres Pro Standard 11.8.1 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.
Ended support for PTRACK versions lower than 2.0 (1.5 - 1.7) since they contain a critical bug that can cause silent corruption in PTRACK backups that were taken under load. PTRACK 1.x API is retained for backward compatibility although all the functionality is no longer available. It is recommended that you avoid restoring PTRACK backups taken earlier, but if such a need arises, validate any restored cluster instance using the command:
pg_probackup checkdb --amcheck.
Added the optional
tuneargument to the
pg-setup initdbcommand. This argument allows you to choose one of the predefined customized configurations for your database cluster.
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.
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.
Migration to Version 11.9.1
If you are upgrading from Postgres Pro Standard based on the same PostgreSQL major version, it is enough to install the new version into your current installation directory.
numeric_le are actually leakproof, they were not marked as such in Postgres Pro Standard 11.6.1 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 11.7.1 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 VOLATILE
Version 11.7.1 also fixes
SIMILAR TO and POSIX regular expressions that use character classes for icu collations, so you may need to check for objects that use such regular expressions.
Starting from Postgres Pro Standard 11.6.1, the ICU library upgrade does not interfere with the server start. Before connecting to a database using ICU as the default collation, Postgres Pro compares this collation version to the one provided by the ICU library and displays a warning if the collation versions do not match; you may need to rebuild the objects that depend on the default collation if you think the collation change may affect the sort order of your data. To suppress these warnings, you can use the
ALTER COLLATION "default" REFRESH VERSION command, as explained in ALTER COLLATION.
Since pg_probackup delivery model changed in Postgres Pro Standard 11.2.1, 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.
To migrate from PostgreSQL or a Postgres Pro Standard release based on a previous PostgreSQL major version, see the migration instructions for version 11. If you are opting for a dump/restore, make sure to use the
--add-collprovider option to correctly choose the provider for the default collation of the migrated database.