E.4. Postgres Pro Enterprise 10.4.1

E.4.1. Overview
E.4.2. Migration to Version 10.4.1

Release date: 2018-06-01

E.4.1. Overview

This release is based on Postgres Pro Standard 10.4.1 and Postgres Pro Enterprise 10.3.3. All changes inherited from Postgres Pro Standard 10.4.1 are listed in Postgres Pro Standard 10.4.1 Release Notes. As compared with Postgres Pro Enterprise 10.3.3, this version provides the following changes:

  • Added an experimental prioritization feature that allows to slow down a particular session based on the assigned weight of this session and the amount of resources it consumes. (See Section 18.4.6.)

  • Implemented the following libpq options for multi-host connections:

    • hostorder parameter that defines the order in which to connect to the hosts.

    • failover_timeout parameter to allow several reconnection attempts.

  • Updated pg_wait_sampling module.

  • Updated in_memory module.

  • Added reusepass configuration option that forbids reusing the prompted password when reconnecting to the database.

  • Added compress_temp_relations to enable compression of temporary tables.

  • Fixed logical replication between vanilla PostgreSQL and Postgres Pro Enterprise.

  • Fixed an issue with GiST indexes on columns of the intarray type. Make sure to run the REINDEX command to rebuild GiST and SP-GiST indexes.

  • Fixed escaping rules for configuration variables in multimaster.

  • Fixed invalid page reference in VALGRIND_CHECK_MEM_IS_DEFINED().

  • Fixed memory issues of aqo module.

E.4.2. Migration to Version 10.4.1

If you are upgrading from a Postgres Pro Enterprise version based on the same PostgreSQL major release, it is enough to install the new version into your current installation directory.

Important

When upgrading from versions 10.3.3 or lower, you must execute the REINDEX command for GiST and SP-GiST indexes, as well as indexes that use mchar or mvarchar types.

To migrate from PostgreSQL, Postgres Pro Standard, or Postgres Pro Enterprise versions based on any previous PostgreSQL major release, see the instructions in Postgres Pro Enterprise 10.1.1 Release Notes. If you are opting for a dump/restore, make sure to use the --add-collprovider option to correctly choose the collation provider for the migrated database.