E.22. Postgres Pro Standard 12.6.1
Release Date: 2021-03-03
E.22.1. Overview
This release is based on PostgreSQL 12.6 and Postgres Pro Standard 12.5.1. All improvements inherited from PostgreSQL 12.6 are listed in PostgreSQL 12.6 Release Notes. Other major changes and enhancements are as follows:
Upgraded pg_probackup to the latest version 2.4.10. Major improvements over the previously included version 2.4.2 are as follows:
Incremental restore with
--forceflag now allows you to overwrite the contents of the directory specified byPGDATAin case of system ID mismatch. Previously this resulted in an error.It is now possible to restore and validate backups from a read-only filesystem.
In-place merge is now disabled only if the storage format changed.
Non-exclusive backup locks are implemented, which enables concurrent validate and restore. Backup shared locks are now released at the process exit.
Streamed WAL segments are now added to the backup filelist on the fly and fsynced to disk at the end of the backup.
See pg_probackup documentation for details.
Fixed a bug that prevented setting
ptrack.map_sizeto values higher than 1024 MB due toint32overflow. See PTRACK for details.Upgraded pgpro_stats. Now it shows resource usage statistics of statement execution, as well as cache invalidation metrics.
Added pgpro_pwr extension. It enables you to generate workload reports, which help to discover most resource-intensive activities in your database.
Added pgpro_controldata utility to display control information of a PostgreSQL/Postgres Pro database cluster and compatibility information for a cluster and/or server.
Added the
pg_snapshot_anyfunction to help superusers explore corrupted databases. See Section 9.26.11 for details.
E.22.2. Migration to Version 12.6.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