E.9. Postgres Pro Standard 12.16.1
Release Date: 2023-08-16
E.9.1. Overview
This release is based onPostgreSQL 12.16 andPostgres Pro Standard 12.15.1. All improvements inherited fromPostgreSQL 12.16 are listed inPostgreSQL 12.16 Release Notes. Other major changes and enhancements are as follows:
Added theenable_appendorpath configuration parameter, which enables the
Appendplan forORclauses. It is useful for applications with auto-generated queries.Added support for Debian 12 and ended support for Debian 9.
Fixed an outdated recommendation to customize a unit file in the
postgrespro-std-12.servicefile comments.Fixed the optimizer estimation of the number of tuples with the same hash key. The optimizer did not take into account that in a join by a large number of columns, the number of unique hash keys must rapidly grow, considered the number of hash keys to be small and finally chose merge join instead of hash join.
Fixed usage of the
joinselcomponent, which is needed for a more accurate cardinality estimation by several columns. If for some reason (for example, because of insufficient detailed statistics)joinselcannot make a good prediction,Postgres Pro will not usejoinselin this particular case, but estimate cardinality using a regular algorithm. Ifjoinselhas to estimate cardinality by a single column, a regular algorithm will also be used instead.Fixed a bug that did not allow storing data of the
mchar,mvarchartypes larger than 250 MB. Now up to 1 GB of data of these types can be stored correctly.Upgradedpg_probackup to version 2.6.5, which provides optimizations and bug fixes.
An attempt of a partial restore to a non-empty
PGDATAdirectory now completes with an error, but a possibility of such a restore is retained with the--destroy-all-other-dbsflag specified.Fixed inclusion of allocated but empty pages in an incremental backup.
Fixed point-in-time recovery issues:
Restore on the recovery time specified by the
pg_probackup showcommandRestore from backups with the
--recovery-target-timelineand--no-validateoptions
Renamed the
--skip-if-existflag to--skip-if-exists
Upgradedpgpro_pwr to version 4.2, which adds interactive features to the report.
UpgradedPTRACK to version 2.5 Enterprise.
E.9.2. Migration to Version 12.16.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.