E.6. Postgres Pro Enterprise 10.7.1
Release date: 2019-03-26
This release is based on PostgreSQL 10.7 and Postgres Pro Enterprise 10.6.2. All changes inherited from PostgreSQL 10.7 are listed in PostgreSQL 10.7 Release Notes. Other major changes and enhancements are as follows:
Fixed processing of queries with multiple
ORclauses to eliminate duplicate results and ensure the correct sort order.
Fixed an issue that could cause server failures when using non-strict aggregate functions.
Provided multiple improvements for autonomous transactions:
Improved SQL syntax consistency: the
AUTONOMOUSkeyword can now be used with
ABORT) transaction statements. Previously, only
BEGINallowed this keyword.
Fixed miscellaneous bugs to improve stability of autonomous transactions.
Changed delivery model for pg_probackup utility:
On Linux, pg_probackup is now provided in the
pg-probackup-ent-10package. On ALT Linux and Debian-based systems, when upgrading from Postgres Pro Enterprise 10.6.2 or lower, run
apt-get dist-upgrade) to ensure that all new dependencies are handled correctly.
On Windows, pg_probackup now has a separate installer. You have to install core components of the current Postgres Pro version before installing pg_probackup.
Added new options to Postgres Pro interactive installer for Windows. Now you can:
libcas the provider for the default collation. Previously, Postgres Pro Enterprise always used
Select a Windows user that starts Postgres Pro service. By default, Postgres Pro service is started on behalf of
Started delivering pg_hint_plan separately:
On Linux, pg_hint_plan is now provided in the
On Windows, pg_hint_plan now has a separate installer that should be run after the core components of the current Postgres Pro version are installed.
Fixed an issue in the pg_hint_plan module that caused server failures when
SeqScanhints were used to enforce sequential scans instead of parallel index scans.
On SUSE Linux Enterprise Server and RHEL-based systems, moved several utilities to different packages for consistency with other Linux distributions: pg_receivewal and pg_recvlogical are delivered as part of the
postgrespro-ent-10-clientpackage, while pg_rewind, pg_waldump, pg_upgrade are now located in the
Backported the patch that addresses
dsm_attach()race condition when DSM handles are reused; in vanilla PostgreSQL, this fix is targeted for the future updates only. The patch is hoped to resolve issues when the server reports the following error message:
ERROR: dsa_area could not attach to segment.
Fixed pg_upgrade to avoid issues with domain constraints that depend on collations. Such constraints are now validated during the upgrade, while in the previous Postgres Pro versions they were always marked as invalid in the new cluster.
Fixed pg_dump and pg_dumpall to correctly work with Postgres Pro Standard databases.
Fixed the pg-setup script so that it can initialize a cluster in a non-default location when run with the
bloomindexes are now tracked correctly by pg_probackup in the
Fixed performance degradation for index-only scans over wide indexes.
Ended support for ALT Linux SPT 6.0 and Windows 7 SP1.
pg_pathmanmodule to version 1.5.5. As compared to version 1.5.2 provided in the previous Postgres Pro releases, the following enhancements were introduced:
pg_pathmanupgrade scripts to avoid issues caused by a different the number of
pg_pathman1.4 and 1.5 major versions.
Trying to call
pg_pathmanfunctions when this extension is disabled does not cause server failures anymore; now an error is raised instead.
Different partitioning strategies can now be successfully applied to the same table.
pg_variablesmodule to version 1.2:
Added support for array types.
Improved module stability.
Changed empty package handling. An empty package is now removed only after the transaction that emptied it has ended.
(See Section F.51.)
E.6.2. Migration to Version 10.7.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.3.3 or lower, you must execute the
REINDEX command for GiST and SP-GiST indexes, as well as indexes that use
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.