Release date: 2018-10-11
This release is based on Postgres Pro Enterprise 10.5.2 and provides the following changes:
pgbadger now supports the extended log format
of Postgres Pro Enterprise. Its package
got renamed to pgpro-pgbadger.
Added a fix for incorrect calculation of the minimum recovery point on standby servers, which could cause incorrect page references.
Updated the online_analyze module,
so that now it forbids nested ANALYZE calls.
Increased the number of partitions of the shared buffer mapping hash table to 1024, which can improve performance on multi-core systems.
Fixed backup restore on a master server to avoid race conditions when applying two-phase transactions.
For Windows systems, fixed an issue with reloading dictionaries
provided by the shared_ispell module.
Updated pg_probackup to version 2.0.21, which provides the following bug fixes:
Issues related to restoring backups taken on standbys are resolved.
The log-rotation-size and log-rotation-age
parameters are now parsed correctly.
The show command now dynamically changes
width of the displayed output to improve readability for large tables.
The restore command now correctly restores all
symbolic links to tablespaces.
If checksums are enabled, the validate command
now verifies checksums for blocks.
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.