Postgres Pro Standard 12.7.1: release notes


This release is based on PostgreSQL 12.7 and Postgres Pro Standard 12.6.2. All improvements inherited from PostgreSQL 12.7 are listed in PostgreSQL 12.7 Release Notes. Other major changes and enhancements are as follows:

  • Removed the hunspell_ne_np Hunspell dictionary. If you still need it, use the extension from github.

  • Upgraded PTRACK to use a different algorithm for tracking changed pages. This greatly reduces the number of false positives among the changed pages tracked in the PTRACK map and hence the size of PTRACK backups.

  • Fixed a bug that caused queries to fail with an error “geqo failed to make a valid plan” after updating statistics with VACUUM ANALYZE when enable_compound_index_stats was on.

  • Ended support for Ubuntu 16.04 and added support for Ubuntu 21.04.

  • Fixed an issue of installing Postgres Pro on Alt Linux 8.2. For this OS, Postgres Pro now provides a separate package repository, which is different from the repositories of earlier Alt Linux versions.

  • Improved the planner's algorithm of self-join selectivity calculation, which ensures more accurate estimates of the number of rows after joins.

  • Upgraded mamonsu to version 2.7.1.

  • Upgraded pgpro_controldata to version 13.2.0.

Migration to Version 12.7.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.