E.11. Postgres Pro Standard 13.10.1
Release Date: 2023-02-20
E.11.1. Overview
This release is based on PostgreSQL 13.10 and Postgres Pro Standard 13.9.1. All improvements inherited from PostgreSQL 13.10 are listed in PostgreSQL 13.10 Release Notes. Other major changes and enhancements are as follows:
Added support for ROSA COBALT Server 7.9 and ended support for ROSA COBALT Server 7.3.
Fixed suboptimal memory usage in optimizing a query that included a pretty large number of
UNION ALL
subqueries. This planner issue was due to a vanilla PostgreSQL issue with replacing placeholder variables in a special case of flatteningUNION ALL
leaf queries.Upgraded aqo to version 1.6, which provides the following new features:
Introduced smart statement timeout, which is needed to limit the execution time when manually training aqo on special queries with a poor cardinality forecast and which aqo can dynamically change during this training.
Added
aqo_query_stat_update
,aqo_data_update
andaqo_query_texts_update
functions to update or insert a record in data files underlying the respective view.Added
aqo_memory_usage
function to display the memory size required for aqo.Renamed
aqo_enable_query
andaqo_disable_query
functions toaqo_enable_class
andaqo_disable_class
, respectively.
Upgraded pg_probackup to version 2.6, which provides the following changes:
Optimized pg_probackup input/output engine to improve performance.
Ended support for Postgres Pro 9.6.
Upgraded pgbouncer to version 1.18.
Upgraded pgpro_stats to version 1.5, which provides new features and bugfixes:
Added computation of statistics on removal of all-frozen and all-visible marks in the visibility map.
Added the
pgpro_stats_vacuum_database
view, showing statistics about vacuuming each database in a cluster.Fixed possible crash of a server where
pgpro_stats.track
was set toall
that could occur when pgpro_stats processed a function body as a multistatement query.Fixed inappropriate issuing of an “unrecognized expression node type: ...” warning in case a query plan contained a GatherMerge node.
Fixed too long execution of a query containing texts of JSON or XML documents of a special kind. The slowdown was possible because normalization of the query plan text could mistakenly include replacement of constants inside those documents.
E.11.2. Migration to Version 13.10.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.
When upgrading from Postgres Pro versions 13.2.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 13.2.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 instructions in Postgres Pro Standard 13.1.1 Release Notes.