E.17. Postgres Pro Enterprise 9.6.10.1
Release date: 2018-08-31
E.17.1. Overview
This release is based on PostgreSQL 9.6.10 and Postgres Pro Enterprise 9.6.9.2. All improvements inherited from PostgreSQL 9.6.10 are listed in PostgreSQL 9.6.10 Release Notes.
Main changes over Postgres Pro Enterprise 9.6.9.2 are as follows:
On Debian-based systems, library packages
libecpg-compat3,libecpg6,libecpg-dev,libpgtypes3,libpq5,libpq-devprovided with Postgres Pro Enterprise got renamed and now have apostgrespro-prefix. When upgrading from a previous version of Postgres Pro Enterprise, runapt-get dist-upgradeto handle this change in an automated way, or install the new packages manually.Updated pg_pathman module to version 1.4.13. For a full list of changes, see pg_pathman Wiki.
Log files now include the number of rows and the size of the data passed to the client if
log_durationis enabled or if the query runs longer thanlog_min_duration_statement.The cfs_compress_temp_relations variable enables/disables compression of temporary tables.
The
pg_variablesmodule now supports transactional variables. (See Section F.49.)The
auto_explainmodule can now display planning time.Autovacuum now immediately drops orphaned temporary tables to prevent
pg_classbloating.Fixed a bug that made unusable some Hunspell dictionaries with
FLAG numaffixes, such asru_aot.Updated pg_probackup module to version 2.0.19, which includes the following new features:
If one of its parent backups is corrupt, the incremental backup is marked with the
ORPHANstatus.The
show-configcommand 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
restorecommand 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.
Miscellaneous bug fixes.
E.17.2. Migration to Version 9.6.10.1
Depending on your current installation, the upgrade procedure will differ.
To migrate from vanilla PostgreSQL 9.6.x or Postgres Pro, make sure you have installed its latest minor version and then perform a dump/restore using pg_dumpall.
To upgrade from a Postgres Pro Enterprise version based on the same PostgreSQL major release, a dump/restore is not required. It is usually enough to install the new version into the same installation directory. Once the new binaries are installed, the pgpro_upgrade script is run automatically to check whether additional setup is required and complete the upgrade.
When upgrading from versions 9.6.8.2 or lower, you have to rebuild indexes that used mchar or mvarchar types.
When upgrading from versions 9.6.2.1 or lower, you have to rebuild GiST indexes built over columns of the intarray type.
When upgrading from version 9.6.1.2 on RPM-based Linux distributions, make sure to move the data directory from pgsql to the pgproee directory before running the pgpro_upgrade script.
For some Linux distributions, you may be prompted to run pgpro_upgrade manually. In this case, you must stop the postgres service. The script must be run on behalf of the user owning the database (typically postgres) and PGDATA environment variable should be set to the directory where database resides. Running pgpro_upgrade as root will result in an error. This step is not required when upgrading from version 9.6.4.1 or higher.