## E.7. Postgres Pro Standard 10.6.1

Release Date: 2018-11-20

### E.7.1. Overview

This release is based on PostgreSQL 10.6 and Postgres Pro Standard 10.5.3. All changes inherited from PostgreSQL 10.6 are listed in PostgreSQL 10.6 Release Notes. Other major changes and enhancements are as follows:

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

- Updated pg-setup :

  - This script can now initialize the database cluster in a non-default location and store the corresponding `PGDATA` value in a system configuration file.

  - You can now run pg-setup with the `set` option to modify cluster configuration.

- Enabled NUL byte replacement with the specified ASCII code while loading data using the `COPY FROM` command. See nul_byte_replacement_on_import parameter description for details.

- Upgraded the `amcheck` extension to version 1.1.

- Improved plantuner stability and fixed a memory leak.

- 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.

### E.7.2. Migration to Version 10.6.1

If you are upgrading from a Postgres Pro Standard version based on the same PostgreSQL major release, it is enough to install the new version into your current installation directory.

When upgrading from version 10.3.2 or lower, you must call the `REINDEX` command for indexes that used `mchar` or `mvarchar` types. Besides, if you have been using `pg_repack` on Debian-based systems, you have to reinstall its package manually when upgrading to this version since its package got renamed to `pg-repack-std-10`.

To migrate from PostgreSQL or a Postgres Pro Standard release based on a previous PostgreSQL major version, see the instructions in Postgres Pro Standard 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 provider for the default collation of the migrated database.