Release date: 2018-09-03
This release is based on PostgreSQL 10.5 and Postgres Pro Enterprise 10.4.1. All changes inherited from PostgreSQL 10.5 are listed in PostgreSQL 10.5 Release Notes. As compared with Postgres Pro Enterprise 10.4.1, this version provides the following changes:
Log files now include the number of rows and the size of the data
passed to the client if log_duration is enabled
or if the query runs longer than log_min_duration_statement.
You can allow the primary server to continue running even if some of its synchronous standbys are disconnected or lag behind for more than the specified threshold. This can result in shorter downtime of the primary when using synchronous replication. For details, see synchronous_standby_names and synchronous_standby_gap.
Updated pg_pathman module to version 1.4.13. For a full list of changes, see pg_pathman Wiki.
Updated multimaster module.
Updated in_memory module.
Updated vops module.
Miscellaneous bug fixes.
The pg_variables module now
supports transactional variables. (See Section F.51.)
The auto_explain module can now display planning
time.
Fixed a bug that made unusable some Hunspell dictionaries with
FLAG num affixes, such as ru_aot.
Updated pg_probackup module to version 2.0.19, which includes the following new features:
You can now restore the cluster up to the specified LSN.
If one of its parent backups is corrupt, the incremental backup
is marked with the ORPHAN status.
The show-config command now shows
both modified pg_probackup
parameters and the default settings that remained unchanged.
The output can be formatted as JSON for better readability.
The restore command can now skip
backup validation to speed up cluster recovery.
Parallel execution of incremental backups has been improved.
You can merge incremental backups to their parent full backup to save disk space. This is an experimental feature that can cause backup corruption if the merge is interrupted.
Postgres Pro Enterprise version for Windows has been improved:
Lifted an implicit restriction on the number of simultaneously open files for each server subprocess.
Added an option to disable data checksums for your cluster. By default, Postgres Pro is installed with data checksums enabled.
Added support for the pg_probackup module.
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,
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.