Movatterモバイル変換

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

• Improvedplantuner stability and fixed a memory leak.

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

• Planning for queries with multipleOR operators in theWHERE clause has been improved.

• Updatedpg_pathman module to version 1.5.2. As compared to version 1.4.14 provided in the previousPostgres Pro releases, the following enhancements were introduced:

  • Added support for multilevel partitioning.

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

  • Renamedget_pathman_lib_version() topathman_version().

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

• Updatedpg_probackup module to version 2.0.24. As compared to version 2.0.19 provided in the previousPostgres 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 inpg_probackup.conf is now preserved when this file gets updated, which allows to correctly identifypg_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 thezlib algorithm failed to compress during backup. This issue could not be detected by the built-inpg_probackup validation mechanism as it occurs on a lower level that validation itself. You are recommended to re-validate existing backups using thispg_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 ofPostgres Pro:

  • PL/Perl now requires ActivePerl 5.26.

  • 32-bitPostgres Pro version is no longer provided.

Note

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

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 frompgsql to thepgpro directory before running thepgpro_upgrade script.