E.14. Postgres Pro Standard 13.10.1
Release Date: 2023-02-20
E.14.1. Overview
This release is based onPostgreSQL 13.10 andPostgres Pro Standard 13.9.1. All improvements inherited fromPostgreSQL 13.10 are listed inPostgreSQL 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 ALLsubqueries. This planner issue was due to a vanillaPostgreSQL issue with replacing placeholder variables in a special case of flatteningUNION ALLleaf queries.Upgradedaqo to version 1.6, which provides the following new features:
Introducedsmart statement timeout, which is needed to limit the execution time when manually trainingaqo on special queries with a poor cardinality forecast and whichaqo can dynamically change during this training.
Added
aqo_query_stat_update,aqo_data_updateandaqo_query_texts_updatefunctions to update or insert a record in data files underlying the respective view.Added
aqo_memory_usagefunction to display the memory size required foraqo.Renamed
aqo_enable_queryandaqo_disable_queryfunctions toaqo_enable_classandaqo_disable_class, respectively.
Upgradedpg_probackup to version 2.6, which provides the following changes:
Optimizedpg_probackup input/output engine to improve performance.
Ended support forPostgres Pro 9.6.
Upgradedpgbouncer to version 1.18.
Upgradedpgpro_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_databaseview, showing statistics about vacuuming each database in a cluster.Fixed possible crash of a server where
pgpro_stats.trackwas set toallthat could occur whenpgpro_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.14.2. Migration to Version 13.10.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.
When upgrading fromPostgres 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 fromPostgres Pro versions 13.2.2 or lower and takePTRACK backups usingpg_probackup, retake a full backup after upgrade.
To migrate fromPostgreSQL or aPostgres Pro Standard release based on a previousPostgreSQL major version, see the instructions inPostgres Pro Standard 13.1.1 Release Notes.