E.6. Postgres Pro Standard 16.3.1#
Release Date: 2024-05-23
E.6.1. Overview#
This release is based onPostgreSQL 16.3 andPostgres Pro Standard 16.2.2. All improvements inherited fromPostgreSQL 16.3 are listed inPostgreSQL 16.3 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 an issue of not streaming certain data to a subscriber by a logical replication after executing the
ALTER PUBLICATION pub ADD TABLE tabcommand. The root cause of the issue was an insufficient interlocking betweenALTER PUBLICATIONand taking a snapshot.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.Added support for Astra Linux 1.8 and ended support for Astra Linux Orel 2.12 and Astra Linux Smolensk 1.6.
Added support for Ubuntu 24.04.
Added support for Red OS Murom 8.
Upgradedaqo to version 2.1, which added theaqo.wal_rw configuration parameter to enable physical replication and allow completeaqo data recovery after failure.
Added thedbcopies_decoding 1C module for updating database copies. It is implemented as a logical replication plug-in and provided in
postgrespro-std-16-contrib.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.Added thepgvector extension that provides vector similarity search forPostgres Pro.
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.
E.6.2. Migration to Version 16.3.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.
To migrate fromPostgreSQL or aPostgres Pro Standard release based on a previousPostgreSQL major version, see the instructions inPostgres Pro Standard 16.0.1 Release Notes.