E.9. Postgres Pro Standard 12.15.1
Release Date: 2023-05-19
E.9.1. Overview
This release is based on PostgreSQL 12.15 and Postgres Pro Standard 12.14.1. All improvements inherited from PostgreSQL 12.15 are listed in PostgreSQL 12.15 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 pgpro_stats to version 1.6, which provides new features and bugfixes:
Implemented tracing of application sessions, based on filters, which trigger logging the execution of queries that match filtering conditions. You can use pgpro_stats functions to create, update or delete query filters. (See Section F.37.6.1 for details.)
Added functions for superuser to create views that emulate pg_stat_statements and pg_stat_kcache extensions. Specifically,
pg_stat_statements,pg_stat_statements_info,pg_stat_kcacheandpg_stat_kcache_detailviews can be created. Once they are created, you can work with them as if the appropriate extension is installed. (See Section F.37.6.2 for details.)Added
pgpro_stats_archiverview, which extends the pg_stat_archiver view by adding two fields, showing overall time that the archiver process was active and overall execution time of the archive command.Implemented backward compatibility of the vacuum statistics interface. Now a newer version of the pgpro_stats shared library can be safely used with old declarations of SQL functions. Previously such cases caused a server crash.
Fixed possible server crashes that could occur due to
PGDATAoverflow when in pgpro_stats, one or several long queries were executed. Now instead of storing query texts in a temporary file located in thePGDATA/pg_stat_tmppgpro_stats.stats_temp_directoryconfiguration parameter. If you wish, you can set this value equal to the value of the system configuration parameterstats_temp_directory. But keep in mind thatpgpro_stats.stats_temp_directorycan only be set at the server start.
Upgraded pgpro_pwr to version 4.1.3, which supports pgpro_stats 1.6 and provides the following new features:
Added report tables “Top tables by removed all-visible/all-frozed marks”.
Added a few new fields to the “Cluster Statistics” report table.
Upgraded PTRACK to version 2.4.3.
Upgraded orafce to version 4.2.6.
E.9.2. Migration to Version 12.15.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 12.1.1, which could lead to incorrect query optimization. In particular, it negatively affected query execution if row-level security policy was in use. Version 12.2.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
When upgrading from Postgres Pro versions 12.6.1 or lower, rebuild 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 12.6.2 or lower and take PTRACK backups using pg_probackup, retake a full backup after upgrade.