E.16. Postgres Pro Standard 11.11.1
Release Date: 2021-02-20
E.16.1. Overview
This release is based onPostgreSQL 11.11 andPostgres Pro Standard 11.10.1. All improvements inherited fromPostgreSQL 11.11 are listed inPostgreSQL 11.11 Release Notes. Other major changes and enhancements are as follows:
Upgradedpg_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.
Seepg_probackup documentation for details.
Fixed a bug that prevented setting
ptrack.map_sizeto values higher than 1024 MB due toint32overflow. SeePTRACK for details.Addedpgpro_controldata utility to display control information of aPostgreSQL/Postgres Pro database cluster and compatibility information for a cluster and/or server.
Added the
pg_snapshot_anyfunction to help superusers explore corrupted databases. SeeSection 9.26.11 for details.
E.16.2. Migration to Version 11.11.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 11.6.1 or lower, which could lead to incorrect query optimization. In particular, it negatively affected query execution if row-level security policy was in use. Version 11.7.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
Version 11.7.1 also fixesSIMILAR TO and POSIX regular expressions that use character classes for icu collations, so you may need to check for objects that use such regular expressions.
Starting fromPostgres Pro Standard 11.6.1, the ICU library upgrade does not interfere with the server start. Before connecting to a database using ICU as the default collation,Postgres Pro compares this collation version to the one provided by the ICU library and displays a warning if the collation versions do not match; you may need to rebuild the objects that depend on the default collation if you think the collation change may affect the sort order of your data. To suppress these warnings, you can use theALTER COLLATION "default" REFRESH VERSION command, as explained inALTER COLLATION.
Sincepg_probackup delivery model changed inPostgres Pro Standard 11.2.1, when upgrading from a lower version on ALT Linux and Debian-based systems, runapt dist-upgrade (orapt-get dist-upgrade) to ensure that all new dependencies are handled correctly. On Windows, you have to run a separatepg_probackup installer to complete the upgrade.
To migrate fromPostgreSQL or aPostgres Pro Standard release based on a previousPostgreSQL major version, see themigration instructions for version 11. If you are opting for a dump/restore, make sure to use the--add-collprovider option to correctly choose the provider for the default collation of the migrated database.