E.14. Postgres Pro Standard 12.12.1
Release Date: 2022-08-29
E.14.1. Overview
This release is based onPostgreSQL 12.12 andPostgres Pro Standard 12.11.2. All improvements inherited fromPostgreSQL 12.12 are listed inPostgreSQL 12.12 Release Notes. Other major changes and enhancements are as follows:
Resolved an issue that caused an error“duplicate key value violates unique constraint” when indexing a database in multiple threads. Now the chosen name of a type being created for the index gets locked to avoid choosing the same name in a parallel process.
Resolved an issue in the planner's use of the compound indexes statistics: the optimizer reduced the cost prediction accuracy for a query plan if in the
WHEREclause of the query, values of different types were compared (for example:integerandnumeric,textandname). Sometimes, for certain combinations of the compared types and values, the issue could cause a server crash.Ended support for Ubuntu 21.10.
Upgradedmamonsu to version 3.5.1. Notable changes are as follows:
Enabledmamonsu plugins to usepgpro_stats to collect statistics.
Resolved the security issue of exposing passwords through the configuration file. Only
mamonsuuser can accessagent.confnow.Fixed metrics computation that caused“float division by zero” errors in themamonsuSTATEMENTS plugin.
Upgradedpg_probackup to version 2.5.7, which provides the following new features and bugfixes:
Upgradedpgpro_pwr to version 4.0.
Added theoracle_fdw package for Red OS Murom 7.3.
E.14.2. Migration to Version 12.12.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
When upgrading fromPostgres 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 fromPostgres Pro versions 12.6.2 or lower and takePTRACK backups usingpg_probackup, retake a full backup after upgrade.