E.29. Postgres Pro Enterprise 11.5.1
Release date: 2019-08-14
E.29.1. Overview
This release is based on PostgreSQL 11.5 and Postgres Pro Enterprise 11.4.2. All changes inherited from PostgreSQL 11.5 are listed in PostgreSQL 11.5 Release Notes. As compared with Postgres Pro Enterprise 11.4.2, this version also provides the following changes:
Added support for Debian 10.
Added support for Red Hat Enterprise Linux 8.
Added
-z/-Zoptions to postgres that check compatibility between the specified cluster and the current postgres binary without starting the cluster.Fixed a memory allocation issue that could occur if the plan_cache_lru_size feature was used, which is enabled in Postgres Pro Enterprise by default.
Fixed
VACUUMlogic for truncating multixact members as required for 64-bit transaction and multixact IDs. It resolves a bloating issue that could affect thepg_multixactdirectory.Backported an optimization for the
PostmasterIsAlive()check. On Linux systems, backends now use signals to determine that postmaster has died. In particular, it fixes an issue withpg_walbloating and high CPU load when logical replication with multiple publications and subscriptions is used. In vanilla PostgreSQL, this optimization appears in version 12.Improved handling of dead tuples for B-tree indexes that perform key deduplication.
Improved planning accuracy for queries with
ORclauses. Now sorting is performed correctly for such queries.Fixed implementation of greater than (>) and not equal to (<>) operators for the
jsquerytype.Fixed a deadlock issue in the pg_wait_sampling module. Previously, a deadlock could occur if clients got disconnected before receiving the requested statistics on wait events. Now statistics collector releases the exclusive lock in such cases and logs the following message:
pg_wait_sampling collector: receiver of message queue has been detached.Improved the multimaster module:
Added support for autonomous transactions on multi-master clusters (see Chapter 16).
Fixed an issue in multimaster that resulted in a rollback of the first transaction on a backend if this transaction set repeatable read or serializable isolation level. This issue manifested itself in the following error message:
ERROR: SET TRANSACTION ISOLATION LEVEL must be called before any query.Fixed an issue in the
mtm.make_table_local()function that could cause hanging and interfere with node recovery.
E.29.2. Migration to Version 11.5.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.
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.