## E.28. Postgres Pro Standard 10.5.3

Release Date: 2018-10-11

### E.28.1. Overview

This release is based on Postgres Pro Standard 10.5.2 and provides the following improvements:

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

### E.28.2. Migration to Version 10.5.3

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.

### Important

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

### Important

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 Postgres Pro Standard versions based on any previous PostgreSQL major release, 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 collation provider for the migrated database.