E.4. Postgres Pro Standard 12.19.1
Release Date: 2024-05-20
E.4.1. Overview
This release is based onPostgreSQL 12.19 andPostgres Pro Standard 12.18.2. All improvements inherited fromPostgreSQL 12.19 are listed inPostgreSQL 12.19 Release Notes. Other major changes and enhancements are as follows:
Disabled the system startup timeout by setting the
TimeoutSecparameter to 0 insystemd. Previously, big databases could fail to start within the specified timeout.Reduced logging level during a specified restore point creation at a checkpoint timeout for inactive bases only. It allows removing excessive log messages.
Fixed a bug resulting in error“cache lookup failed for collation 128”. Now, for the additional
INCLUDEindex columns, collation is ignored.Fixed two planner issues. An expression duplication issue previously caused underestimation of node selectivity and cost in some cases, which could lead to a choice of a suboptimal plan. Another issue — the selectivity overestimation for an
AppendOrnode was caused by its subnode selectivity overestimation and led to the plan cost overestimation.Ended support for Astra Linux Orel 2.12.
Ended support for Astra Linux Smolensk 1.6.
Ended support for Red OS Murom 7.2.
Upgradedmamonsu to version 3.5.8, which provides optimizations and bugfixes. Notable changes are as follows:
Added support for theZabbix 6.4 API: handling of deprecated parameters for authentication requests.
Removed caching of the
pgsql.connections[max_connections]metric.Updated the default log rotation rules.
Prepared for support of Python 3.12.
Changed metric names of thepg_locks plugin. Be aware that the changes could break custom user-defined triggers and processing functions that use the
item.nameparameter.Fixed type mismatch forpgpro_stats andpg_wait_sampling.
Fixed privileges for the
mamonsurole created bybootstrap.
Upgradedorafce to version 4.10.0.
Upgradedpg_probackup to version 2.8.0, which provides new features, optimizations and bug fixes. Notable changes are as follows:
Added a possibility to limit the rate of disk writes using the option
--write-rate-limit=bitrate (Mbps, Gbps).Decreased the memory consumption when restoring long sequences of increments twice on average.
Added a possibility to validate only a WAL archive.
Extended the use of the
--dry-runoption for allpg_probackup commands.Made creation of a temporary slot during backups in the STREAM mode the default behavior unless it is specified otherwise.
Changed the default compression algorithm to
zstd. Ifzstdis not supported by the system,lz4has the next priority. The--compressoption now sets the default values for--compress-leveland--compress-algorithm.
Added the
pgv_exists_elemfunction topg_variables that checks whether an element with a key exists in a general collection.Upgradedpgpro_stats to version 1.7.1, which provides optimizations and bug fixes. Notable changes are as follows:
Added saving non-normalized plans topgpro_stats for queries where previously no plans were saved.
Fixed an issue that hindered the monitoring when the
pgpro_stats_statementsview contained quite a few rows with the same values ofplanandqueryid, but different values ofplanid. The issue was caused by an error in parsing the plan tree containing aT_Memoisenode.
Upgradedpgpro_pwr to version 4.5.
Fixed an error“ERROR: query failed: ERROR: tablespace "XXXX" does not exist” that could occur when the
pg_repackcommand was trying to reorganize tables in a tablespace whose name started with a digit. The root cause of the issue was thatpg_repack expected extra quotes.Added the
--save-fullpageoption topg_waldump. It allows saving full-page images included in WAL records into a given target directory.
E.4.2. Migration to Version 12.19.1
If you are upgrading fromPostgres Pro Standard based on the samePostgreSQL major version, 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 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 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
When upgrading fromPostgres 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 fromPostgres Pro versions 12.6.2 or lower and takePTRACK backups usingpg_probackup, retake a full backup after upgrade.