Postgres Pro Standard 9.6.11.1: release notes

Overview

This release is based on PostgreSQL 9.6.11 and Postgres Pro Standard 9.6.10.3. All improvements inherited from PostgreSQL 9.6.11 are listed in PostgreSQL 9.6.11 Release Notes.

Major enhancements over Postgres Pro Standard 9.6.10.3 include:

  • Added support for Ubuntu 18.10, Astra Linux Smolensk 1.6, and Red OS Murom 7 operating systems.

  • Improved plantuner stability and fixed a memory leak.

  • Fixed an issue in index search that caused a slowdown when using complex jsquery values.

  • Planning for queries with multiple OR operators in the WHERE clause has been improved.

  • Updated pg_pathman module to version 1.5.2. As compared to version 1.4.14 provided in the previous Postgres Pro releases, the following enhancements were introduced:

    • Added support for multilevel partitioning.

    • Eliminated update triggers and added pg_pathman.enable_partitionrouter parameter to enable/disable cross-partition updates.

    • Renamed get_pathman_lib_version() to pathman_version().

    • Provided other miscellaneous bug fixes and improvements. For a full list of changes, see pg_pathman Wiki.

     

  • Updated pg_probackup module to version 2.0.24. As compared to version 2.0.19 provided in the previous Postgres Pro releases, the following enhancements were introduced:

    • If unchanged since the previous backup, files that do not store relation data are now skipped in incremental backups.

    • Version number specified in pg_probackup.conf is now preserved when this file gets updated, which allows to correctly identify pg_probackup version used to take the backup.

    • Fixed an issue with restoring compressed file blocks and enhanced checks for compression errors. Previously, pg_probackup could not restore file blocks that the zlib algorithm failed to compress during backup. This issue could not be detected by the built-in pg_probackup validation mechanism as it occurs on a lower level that validation itself. You are recommended to re-validate existing backups using this pg_probackup version.

    • Improved validation algorithm. Files are now validated block by block by default, not only in case of file-level checksum mismatch. You can disable this behavior using the --skip-block-validation option.

    • Allowed restarting a backup merge if the previous attempt has been interrupted.

    • Allowed taking backups from standby servers without connecting to the master. Besides, pg_probackup now uses its built-in mechanism to determine the consistency point, so there is no risk that backups from standby contain any inconsistent data.

  • Introduced the following changes for Windows version of Postgres Pro:

    • PL/Perl now requires ActivePerl 5.26.

    • 32-bit Postgres Pro version is no longer provided.

     

Migration to Version 9.6.11.1

Depending on your current installation, the upgrade procedure will differ.

To upgrade from a Postgres Pro Standard version based on any previous PostgreSQL major release, you can perform a dump/restore using pg_dumpall, or use the pg_upgrade utility. The first option is safer, while the second is faster and can significantly speed up the upgrade process for large databases.

To upgrade from a Postgres Pro Standard version based on the same PostgreSQL major release, a dump/restore is not required.

When upgrading from versions 9.6.8.2 or lower, you must call the REINDEX command for indexes that used mchar or mvarchar types.

If you are upgrading from Postgres Pro Standard 9.6.7.1 or lower, you must also use the pgpro_upgrade script provided in this distribution. This script updates metadata information to handle catalog number format change introduced after Postgres Pro Standard 9.6.4.1, as well as rename the pgpro_build function to pgpro_source_id. If you are upgrading your Postgres Pro installation from a binary package, the pgpro_upgrade script is run automatically, unless you are prompted to run it manually.

Note

If you run pgpro_upgrade manually, you must stop postgres service. The script must be run on behalf of the user owning the database (typically postgres). Running pgpro_upgrade as root will result in an error. For details, see pgpro_upgrade.

If you have compiled Postgres Pro from source code or created your database in a non-default location, you must run the pgpro_upgrade script manually.

Note

On RPM-based Linux distributions, if you are upgrading from version 9.6.2.1 or lower, make sure to move the data directory from pgsql to the pgpro directory before running the pgpro_upgrade script.

To migrate from vanilla PostgreSQL 9.6.x, perform a dump/restore using pg_dumpall.