E.11. Postgres Pro Standard 12.14.1
Release Date: 2023-02-17
E.11.1. Overview
This release is based on PostgreSQL 12.14 and Postgres Pro Standard 12.13.1. All improvements inherited from PostgreSQL 12.14 are listed in PostgreSQL 12.14 Release Notes. Other major changes and enhancements are as follows:
Added support for ROSA COBALT Server 7.9 and ended support for ROSA COBALT Server 7.3.
Fixed suboptimal memory usage in optimizing a query that included a pretty large number of
UNION ALLsubqueries. This planner issue was due to a vanilla PostgreSQL issue with replacing placeholder variables in a special case of flatteningUNION ALLleaf queries.Upgraded pg_probackup to version 2.6, which provides the following changes:
Optimized pg_probackup input/output engine to improve performance.
Ended support for Postgres Pro 9.6.
Upgraded pgbouncer to version 1.18.
Upgraded pgpro_stats to version 1.5, which provides new features and bugfixes:
Added computation of statistics on removal of all-frozen and all-visible marks in the visibility map.
Added the
pgpro_stats_vacuum_databaseview, showing statistics about vacuuming each database in a cluster.Fixed possible crash of a server where
pgpro_stats.trackwas set toallthat could occur when pgpro_stats processed a function body as a multistatement query.Fixed inappropriate issuing of an “unrecognized expression node type: ...” warning in case a query plan contained a GatherMerge node.
Fixed too long execution of a query containing texts of JSON or XML documents of a special kind. The slowdown was possible because normalization of the query plan text could mistakenly include replacement of constants inside those documents.
E.11.2. Migration to Version 12.14.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.
While functions numeric_eq, numeric_ne, numeric_gt, numeric_ge, numeric_lt, and numeric_le are actually leakproof, they were not marked as such in Postgres 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 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
When upgrading from Postgres Pro versions 12.6.1 or lower, rebuild indexes containing at least one included column of type for which the collation was defined in the table.
If you are upgrading from Postgres Pro versions 12.6.2 or lower and take PTRACK backups using pg_probackup, retake a full backup after upgrade.