E.6. Postgres Pro Standard 10.18.1
Release Date: 2021-08-23
E.6.1. Overview
This release is based onPostgreSQL 10.18 andPostgres Pro Standard 10.17.1. All changes inherited fromPostgreSQL 10.18 are listed inPostgreSQL 10.18 Release Notes. Other major changes and enhancements are as follows:
Upgradedmamonsu to version 3.0, which is incompatible with the previous one. Readmamonsu Compatibility Considerations to learn what you need to do to continue using the application.
Added support for Astra Linux Smolensk 1.7.
Fixed the behavior of
ALTER TABLE IF EXISTScommand in the case when the source table is missing and thepg_pathman extension was loaded. Previously,tableRENAME TOtable1ERRORwas returned, and nowNOTICEis generated, which is howPostgres Pro behaves with nopg_pathman extension loaded.Upgradedpg_probackup to version 2.5.1, which added a new
catchupcommand to copy aPostgres Pro instance directly, without using the backup catalog. This allows you to add a new standby server in a parallel mode or to have a fallen-behind standby server“catch up” with master.Fixed a bug in the query optimizer, which overestimated the cost of index scan using a unique index. This behavior was observed when between index scans using a unique index and using a non-unique one, the non-unique index was chosen, which resulted in excessive disk accesses and a considerable overall slowdown.
E.6.2. Migration to Version 10.18.1
If you are upgrading from aPostgres Pro Standard version based on the samePostgreSQL major release, it is enough to install the new version into your current installation directory.
While functionsnumeric_eq,numeric_ne,numeric_gt,numeric_ge,numeric_lt, andnumeric_le are actually leakproof, they were not marked as such inPostgres Pro Standard 10.11.1 or lower, which could lead to incorrect query optimization. In particular, it negatively affected query execution if row-level security policy was in use. Version 10.12.1 repairs this issue for new installations by correcting the initial catalog data, but existing installations will still have incorrect markings unless you updatepg_proc entries for these functions. You can runpg_upgrade to upgrade your server instance to a version containing the corrected initial data, or manually correct these entries in each database of the installation using theALTER FUNCTION command. For example:
ALTER FUNCTION pg_catalog.numeric_eq LEAKPROOF
Starting fromPostgres Pro Standard 10.11.1, the ICU library upgrade does not interfere with the server start. Before connecting to a database using ICU as the default collation,Postgres Pro compares this collation version to the one provided by the ICU library and displays a warning if the collation versions do not match; you may need to rebuild the objects that depend on the default collation if you think the collation change may affect the sort order of your data. To suppress these warnings, you can use theALTER COLLATION "default" REFRESH VERSION command, as explained inALTER COLLATION.
Sincepg_probackup delivery model changed inPostgres Pro Standard 10.7.1, when upgrading from a lower version on ALT Linux and Debian-based systems, runapt dist-upgrade (orapt-get dist-upgrade) to ensure that all new dependencies are handled correctly. On Windows, you have to run a separatepg_probackup installer to complete the upgrade.
When upgrading from version 10.3.2 or lower, you must call theREINDEX command for indexes that usedmchar ormvarchar types. Besides, if you have been usingpg_repack on Debian-based systems, you have to reinstall its package manually when upgrading to this version since its package got renamed topg-repack-std-10.
To migrate fromPostgreSQL or aPostgres Pro Standard release based on a previousPostgreSQL major version, see themigration instructions for version 10. 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.