E.21. Postgres Pro Standard 12.6.2
Release Date: 2021-04-02
E.21.1. Overview
This release is based onPostgreSQL 12.6 andPostgres Pro Standard 12.6.1. All improvements inherited fromPostgreSQL 12.6 are listed inPostgreSQL 12.6 Release Notes. Other major changes and enhancements are as follows:
Fixed the signed integer overflow inptrack that could occur whenptrack map data in RAM was saved to disk. Previously, for large-sizeptrack maps (
ptrack.mapsize> 17200 MB), this resulted in a“FATAL/ERROR ptrack checkpoint: stat_buf.st_size != ptrack_map_size XXX != YYY” error during a checkpoint.Fixed building of covering indexes with included columns of type for which the collation is defined in the table. The fixed defect could result in an“
ERROR: could not determine which collation to use for string comparison” error during theANALYZE operation on the table, although single columns could be successfully analyzed. To avoid this error in future, after upgrading, rebuild indexes containing at least one included column of such types.
E.21.2. Migration to Version 12.6.2
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.