E.26. Postgres Pro Standard 12.2.1
Release Date: 2020-03-03
E.26.1. Overview
This release is based onPostgreSQL 12.2 andPostgres Pro Standard 12.1.1. All improvements inherited fromPostgreSQL 12.2 are listed inPostgreSQL 12.2 Release Notes. Major enhancements overPostgres Pro Standard 12.1.1 include:
Added theenable_compound_index_stats configuration parameter to control the use of compound indexes statistics for selectivity estimation.
Increased the maximum value of thetrack_activity_query_size parameter to 1MB. In vanillaPostgreSQL, this change is targeted for version 13.
Fixed self join removal functionality to achieve better stability.
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.Optimized execution of queries with Materialize nodes that return nothing; now such nodes are called only once and skipped in all the subsequent runs.
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.
Upgraded themchar module to version 2.1.
Upgradedpg_probackup to version 2.2.7.
Upgradedmamonsu to version 2.4.4.
E.26.2. Migration to Version 12.2.1
If you are upgrading fromPostgres Pro Standard based on the samePostgreSQL major version, 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 12.1.1, which could lead to incorrect query optimization. In particular, it negatively affected query execution if row-level security policy was in use. Version 12.2.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