E.13. Postgres Pro Standard 11.13.1
Release Date: 2021-08-24
E.13.1. Overview
This release is based on PostgreSQL 11.13 and Postgres Pro Standard 11.12.1. All improvements inherited from PostgreSQL 11.13 are listed in PostgreSQL 11.13 Release Notes. Other major changes and enhancements are as follows:
Added support for Debian 11.
Upgraded mamonsu to version 3.0, which is incompatible with the previous one. Read mamonsu 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 the pg_pathman extension was loaded. Previously,tableRENAME TOtable1ERRORwas returned, and nowNOTICEis generated, which is how Postgres Pro behaves with no pg_pathman extension loaded.Upgraded pg_probackup to version 2.5.1, which added a new
catchupcommand to copy a Postgres 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.13.2. Migration to Version 11.13.1
If you are upgrading from Postgres Pro Standard based on the same PostgreSQL major version, it is enough to install the new version into your current installation directory.
While functions numeric_eq, numeric_ne, numeric_gt, numeric_ge, numeric_lt, and numeric_le are actually leakproof, they were not marked as such in Postgres Pro Standard 11.6.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 11.7.1 repairs this issue for new installations by correcting the initial catalog data, but existing installations will still have incorrect markings unless you update pg_proc entries for these functions. You can run pg_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 the ALTER FUNCTION command. For example:
ALTER FUNCTION pg_catalog.numeric_eq LEAKPROOF
Version 11.7.1 also fixes SIMILAR TO and POSIX regular expressions that use character classes for icu collations, so you may need to check for objects that use such regular expressions.
Starting from Postgres Pro Standard 11.6.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 the ALTER COLLATION "default" REFRESH VERSION command, as explained in ALTER COLLATION.
Since pg_probackup delivery model changed in Postgres Pro Standard 11.2.1, when upgrading from a lower version on ALT Linux and Debian-based systems, run apt dist-upgrade (or apt-get dist-upgrade) to ensure that all new dependencies are handled correctly. On Windows, you have to run a separate pg_probackup installer to complete the upgrade.
When upgrading from Postgres Pro versions 11.11.1 or lower, rebuild covering indexes containing at least one included column of type for which the collation was defined in the table.
If you are upgrading from Postgres Pro versions 11.11.2 or lower and take PTRACK backups using pg_probackup, retake a full backup after upgrade.
To migrate from PostgreSQL or a Postgres Pro Standard release based on a previous PostgreSQL major version, see the migration instructions for version 11. 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.