This release is based on PostgreSQL 12.4 and Postgres Pro Standard 12.3.1. All improvements inherited from PostgreSQL 12.4 are listed in PostgreSQL 12.4 Release Notes. Major enhancements over Postgres Pro Standard 12.3.1 include:
Upgraded pg_probackup to latest version 2.4.2:
New options and flags can now be used to add flexibility to
Incremental restore and support for multi-timeline incremental chains have been added.
Postgres Pro parameters
primary_conninfocan be used during restore.
archive-getcommands considerably reworked.
Improvements have been achieved in speed and memory consumption.
See pg_probackup documentation for details.
Added the optional
tuneargument to the
pg-setup initdbcommand. This argument allows you to choose one of the predefined customized configurations for your database cluster.
Ended support for ALT Linux 7, while support for ALT Linux SPT 7 is retained for convenience of existing customers.
Ended support for SUSE Linux Enterprise Server 11.
Fixed race conditions in BRIN index that caused errors:
"failed to find parent tuple for heap-only tuple ...".
The error could occur when the
brin_summarize_new_values()function and HOT updates were executed simultaneously in concurrent transactions.
"corrupted BRIN index: inconsistent range map".
The error could occur when BRIN index's desummarization and a bitmap scan were executed simultaneously in concurrent transactions.
Upgraded mamonsu for Linux systems to version 2.5.1. Now it is based on Python 3. Version 2.3.4 is still provided for Windows systems.
Migration to Version 12.4.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.
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 VOLATILE