E.4. Postgres Pro Standard 11.20.1
Release Date: 2023-05-18
E.4.1. Overview
This release is based on PostgreSQL 11.20 and Postgres Pro Standard 11.19.1. All improvements inherited from PostgreSQL 11.20 are listed in PostgreSQL 11.20 Release Notes. Other major changes and enhancements are as follows:
Added the unicode_nul_character_replacement_in_jsonb configuration parameter to replace
'\u0000'with the specified unicode character when calling a function processing JSONB.Ended support for Ubuntu 18.04.
Upgraded mamonsu to version 3.5.3, which provides new features and bugfixes. Notable changes are as follows:
Removed the limitation that did not allow a user different from
mamonsuto read and edit the configuration fileagent.conf. Specifically, the pg_probackup plugin now works correctly when themamonsuuser owns the pg_probackup backup directory.Removed metrics that conflict native Zabbix agents from Zabbix configuration file being exported.
Fixed mamonsu choice of the default extension to collect statistics. Now when pgpro_stats and pg_stat_statements are both installed, pgpro_stats is correctly treated as the default one.
Added a check that the server where mamonsu WAL plugin runs is not in recovery.
Upgraded pg_probackup to version 2.6.2, which provides the following optimizations and bug fixes:
Included the
catchupcommand, which was previously provided only in a test mode, in the production delivery.Added optimizations for incremental backups that reduce disk read amount almost twice.
Improved error and warning messaging and unified the error message style.
Fixed usability issues with the
showcommand, in particular: fixed displaying the recovery time, which could sometimes not be displayed after a successful backup; made the backup time be displayed in a table view even if the backup ended with an error.Fixed an error in specifying the relative path after restoring a cluster from a backup.
Corrected an improper assignment of backup IDs that took place in some cases.
Upgraded PTRACK to version 2.4.3.
Upgraded orafce to version 4.2.6.
E.4.2. Migration to Version 11.20.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.