E.17. Postgres Pro Enterprise 11.11.1
Release date: 2021-03-02
This release is based on PostgreSQL 11.11 and Postgres Pro Enterprise 11.10.1. All changes inherited from PostgreSQL 11.11 are listed in PostgreSQL 11.11 Release Notes. As compared with Postgres Pro Enterprise 11.10.1, this version also provides the following changes:
cfs_compress_small_relationsparameter. Small relations are still compressed by default and will not differ from the bigger ones. Make sure to keep the existing parameter setting intact for the lifetime of your database cluster.
Fixed a bug in the CFS implementation that resulted in disabling compression for all relations when the
cfs_compress_temp_relationsparameter was set.
pg_snapshot_anyfunction to help superusers explore corrupted databases. See Section 9.26.11 for details.
Aligned the behavior of the parameters
idle_in_transaction_session_timeoutwith how they will behave in a future PostgreSQL release. Specifically, the
idle_session_timeoutparameter now applies only when outside a transaction.
Fixed a bug in the btree compression implementation that could lead to a server crash when processing a tuple deletion in some rare cases.
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 by
PGDATAin 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 to
int32overflow. See PTRACK for details.
Fixed a bug in pgpro_scheduler due to which jobs scheduled to run exactly at the start of an hour (but at a two-hour or larger interval) were not executed at all.
Added pgpro_controldata utility to display control information of a PostgreSQL/Postgres Pro database cluster and compatibility information for a cluster and/or server.
Fixed the behavior of pg_wait_sampling in case of interrupting a client backend that accessed the shared queue. Previously, the pg_wait_sampling collector could hang in such cases and block other backends trying to read the
Fixed a bug in the multimaster extension related to monotonic sequences. Now the parameter
multimaster.monotonic_sequencesbehaves as documented and provides always increasing sequences across all nodes.
E.17.2. Migration to Version 11.11.1
If you are upgrading from a Postgres Pro Enterprise release 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 Enterprise 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 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
Version 11.7.1 also fixes
SIMILAR 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 from Postgres Pro Enterprise 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 the
ALTER COLLATION "default" REFRESH VERSION command, as explained in ALTER COLLATION.
To migrate from PostgreSQL, as well as Postgres Pro Standard or Postgres Pro Enterprise based on a previous PostgreSQL major version, see the migration instructions for version 11.