E.12. Postgres Pro Standard 10.12.1
Release Date: 2020-02-26
E.12.1. Overview
This release is based onPostgreSQL 10.12 andPostgres Pro Standard 10.11.1. All changes inherited fromPostgreSQL 10.12 are listed inPostgreSQL 10.12 Release Notes. Other major changes and enhancements are as follows:
Increased the maximum value of thetrack_activity_query_size parameter to 1MB. In vanillaPostgreSQL, this change is targeted for version 13.
Fixed planner's optimization to correctly take into account similar
ORclauses if they reference columns that are different, but have the same position in different indexes.Fixed the
mcharextension to correctly handle theESCAPEclause inSIMILAR TOregular expressions.Improved query performance with row-level security policy enabled by correctly marking numeric comparison functions as leakproof.
Upgradedpg_probackup to version 2.2.7.
Upgradedmamonsu to version 2.4.4.
E.12.2. Migration to Version 10.12.1
If you are upgrading from aPostgres Pro Standard version based on the samePostgreSQL major release, it is enough to install the new version into your current installation directory.
While functionsnumeric_eq,numeric_ne,numeric_gt,numeric_ge,numeric_lt, andnumeric_le are actually leakproof, they were not marked as such inPostgres Pro Standard 10.11.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 10.12.1 repairs this issue for new installations by correcting the initial catalog data, but existing installations will still have incorrect markings unless you updatepg_proc entries for these functions. You can runpg_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 theALTER FUNCTION command. For example:
ALTER FUNCTION pg_catalog.numeric_eq LEAKPROOF
Starting fromPostgres Pro Standard 10.11.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 theALTER COLLATION "default" REFRESH VERSION command, as explained inALTER COLLATION.
Sincepg_probackup delivery model changed inPostgres Pro Standard 10.7.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 version 10.3.2 or lower, you must call theREINDEX command for indexes that usedmchar ormvarchar types. Besides, if you have been usingpg_repack on Debian-based systems, you have to reinstall its package manually when upgrading to this version since its package got renamed topg-repack-std-10.
To migrate fromPostgreSQL or aPostgres Pro Standard release based on a previousPostgreSQL major version, see themigration instructions for version 10. 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.