E.21. Postgres Pro Enterprise 11.8.1
Release date: 2020-05-28
E.21.1. Overview
This release is based on PostgreSQL 11.8 and Postgres Pro Enterprise 11.7.2. All changes inherited from PostgreSQL 11.8 are listed in PostgreSQL 11.8 Release Notes. As compared with Postgres Pro Enterprise 11.7.2, this version also provides the following changes:
Fixed an issue with an infinite loop that could lead to consuming all the available memory while planning join operations with multiple
INconditions.Fixed an issue that could lead to server failure if autovacuum tried to access a manually dropped temporary namespace.
Fixed an issue that could lead to losing transactional consistency if multiple autonomous transactions were in use.
Enabled index replacement for primary key and exclusion constraints using the
ALTER CONSTRAINT ... USING INDEXclause of the ALTER TABLE command; previously, this functionality was supported only for unique constraints. Besides, index compatibility checks performed during such replacements have been refined.Updated CFS to allow changing the cfs_gc_threshold parameter for the current session. Now you can temporarily set it to a smaller value if you would like to manually defragment a relation with a smaller percent of garbage than is currently allowed.
Fixed a memory leak that could occur during join operations if they required estimating multiple query execution paths for complex queries.
Added the
--no-data-checksumsoption for initdb to allow initializing Postgres Pro clusters with checksums disabled.Optimized writing of empty pages to
*.cfmfiles in base backups.Added support for Oracle Linux 8.
Added support for ALT Linux 8 SP.
Added support for Ubuntu 20.04.
Added the
plpython3package for Rosa Enterprise Linux Server 7, ROSA COBALT (server edition) based on Rosa platform 7, and AlterOS 7.5 distributions where it was previously missing. Now it is available on all supported platforms except SLES 11.Upgraded several libraries provided with Postgres Pro on Windows. Now the following libraries are used: OpenSSL 1.1.1g, libzstd 1.4.4, gettext 0.20.2, libiconv 1.16, libxml2 2.9.9, and libxslt 1.1.32. The ICU library has been upgraded from version 56.1 to 56.2.
Updated the multimaster extension. Now it provides the mtm.check_query(query_text) function for checking data consistency between cluster nodes. For details, see Section F.30.4.6.
Updated amcheck to correctly handle B-tree indexes that use deduplication.
Upgraded pgpro_scheduler to version 2.6. This version introduces several fixes and enhancements, including the following:
Running DDL commands within scheduled tasks does not cause server failure anymore.
pgpro_scheduler now starts scheduled jobs once a background worker becomes available if there were not enough workers to start the job on time.
The implementation of cron parser has been fully reworked.
Upgraded pageinspect to version 1.6 to correctly handle 64-bit transaction IDs.
Updated vops to provide an automated way of generating and accessing vectorized data. For details, see Section F.68.5.5.
Upgraded pg_pathman to version 1.5.11 to avoid server failure when trying to access child partitions without the required permissions while parent table access is allowed. This issue could previously occur when using pg_pathman with Postgres Pro 11.7.1 or higher.
E.21.2. Migration to Version 11.8.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.
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 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.