E.19. Postgres Pro Standard 12.8.1
Release Date: 2021-08-25
E.19.1. Overview
This release is based onPostgreSQL 12.8 andPostgres Pro Standard 12.7.1. All improvements inherited fromPostgreSQL 12.8 are listed inPostgreSQL 12.8 Release Notes. Other major changes and enhancements are as follows:
Added support for Debian 11.
Upgradedmamonsu to version 3.0, which is incompatible with the previous one. Readmamonsu Compatibility Considerations to learn what you need to do to continue using the application.
Added support for Red OS Murom 7.3.
Added support for Astra Linux Smolensk 1.7.
Fixed the behavior of
ALTER TABLE IF EXISTScommand in the case when the source table is missing and thepg_pathman extension was loaded. Previously,tableRENAME TOtable1ERRORwas returned, and nowNOTICEis generated, which is howPostgres Pro behaves with nopg_pathman extension loaded.Upgradedpg_probackup to version 2.5.1, which added a new
catchupcommand to copy aPostgres Pro instance directly, without using the backup catalog. This allows you to add a new standby server in a parallel mode or to have a fallen-behind standby server“catch up” with master.Fixed a bug in the query optimizer, which overestimated the cost of index scan using a unique index. This behavior was observed when between index scans using a unique index and using a non-unique one, the non-unique index was chosen, which resulted in excessive disk accesses and a considerable overall slowdown.
E.19.2. Migration to Version 12.8.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.