E.20. Postgres Pro Standard 12.7.1
Release Date: 2021-05-27
E.20.1. Overview
This release is based onPostgreSQL 12.7 andPostgres Pro Standard 12.6.2. All improvements inherited fromPostgreSQL 12.7 are listed inPostgreSQL 12.7 Release Notes. Other major changes and enhancements are as follows:
Removed the
hunspell_ne_npHunspell dictionary. If you still need it, use the extension fromgithub.UpgradedPTRACK to use a different algorithm for tracking changed pages. This greatly reduces the number of false positives among the changed pages tracked in thePTRACK map and hence the size ofPTRACK backups.
Fixed a bug that caused queries to fail with an error“geqo failed to make a valid plan” after updating statistics with
VACUUM ANALYZEwhenenable_compound_index_statswas on.Ended support for Ubuntu 16.04 and added support for Ubuntu 21.04.
Fixed an issue of installingPostgres Pro on Alt Linux 8.2 SP. For this OS,Postgres Pro now provides a separate package repository, which is different from the repositories of earlier Alt Linux SP versions.
Improved the planner's algorithm of self-join selectivity calculation, which ensures more accurate estimates of the number of rows after joins.
Upgradedmamonsu to version 2.7.1.
Upgradedpgpro_controldata to version 13.2.0.
E.20.2. Migration to Version 12.7.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.