E.21. Postgres Pro Enterprise 10.10.1
Release date: 2019-08-13
E.21.1. Overview
This release is based on PostgreSQL 10.10 and Postgres Pro Enterprise 10.9.1. All changes inherited from PostgreSQL 10.10 are listed in PostgreSQL 10.10 Release Notes. Other major changes and enhancements are as follows:
Added support for Debian 10.
Added support for Red Hat Enterprise Linux 8.
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.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.
E.21.2. Migration to Version 10.10.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.
When upgrading from versions 10.6.2 or lower, you must run the REINDEX command to rebuild GIN, GiST, and SP-GiST indexes to fix replication issues that could be observed in these versions. You should also retake all backups for these versions if your database had such indexes.
When upgrading from versions 10.3.3 or lower, you have to rebuild GiST indexes built over columns of the intarray type, as well as indexes that use mchar or mvarchar types.
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 10. 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.