E.12. Postgres Pro Enterprise 10.4.1

Release date: 2018-06-01

E.12.1. Overview

This release is based on PostgreSQL 10.4 and Postgres Pro Enterprise 10.3.3. All changes inherited from PostgreSQL 10.4 are listed in PostgreSQL 10.4 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 cfs_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.

  • Updated the mchar module to fix the sorting order for Cyrillic letters Yo and short I. Make sure to run the REINDEX command to rebuild indexes that use mchar or mvarchar types.

  • Added full-text search support for the Nepali language into the Snowball and Hunspell dictionaries.

  • Updated jsquery module.

  • Updated PTRACK to version 1.6:

    • Now ptrack doesn't track unlogged relations.

  • Updated the pg_probackup utility to version 2.0.17, which includes the following new features:

    • DELTA mode for incremental backups that reads all data files in the data directory and creates an incremental backup for pages that have changed since the previous backup.

    • New options for restore and validate commands:

      • --immediate option ends recovery as soon as a consistent state is reached.

      • --recovery-target-action option specifies the action the server should take when the recovery target is reached.

      • --recovery-target-name specifies a named savepoint up to which to restore the cluster data.

      • --write-recovery-conf writes a minimal recovery.conf in the output directory to facilitate setting up a standby server.

      For details, see pg_probackup.

  • Updated pg_pathman module to version 1.4.11. As compared to version 1.4.9, the following enhancements were introduced:

    • Fixed an issue with duplicate entries in query results for inherited tables. In general, pg_pathman does not support multilevel partitioning.

    • Fixed a spurious table is being partitioned now error raised by partition_table_concurrently().

    • Relaxed check constraint handling.

    • Fixed incorrect usage of memcpy() in start_bgworker().

    • For a full list of changes, see pg_pathman Wiki.

  • Added pgpro-version and pgpro-edition options to pg_config.

  • The recovery.conf file is now reloaded whenever the main server process receives a SIGHUP signal.

  • Performed multiple bug fixes in the shared_ispell module.

  • On Debian-based systems, renamed the pg_repack package from pg-repack-10 to pg-repack-std-10.

  • Log files are now automatically reopened when a SIGHUP signal is received by the logger process.

  • Improved Postgres Pro Enterprise version for Windows:

    • Fixed an issue with pasting strings that include symbols of different character sets from clipboard to psql on Windows systems.

    • Updated optimization algorithm for default database configuration.

    • You can now turn off configuration optimization when installing Postgres Pro from the command line by setting the needoptimization option in the INI file to 0.

E.12.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.


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, 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.