E.11. Postgres Pro Standard 14.9.1
Release Date: 2023-08-17
E.11.1. Overview
This release is based onPostgreSQL 14.9 andPostgres Pro Standard 14.8.2. All improvements inherited fromPostgreSQL 14.9 are listed inPostgreSQL 14.9 Release Notes. Other major changes and enhancements are as follows:
Added thegeneric_plan_fuzz_factor configuration parameter. This parameter sets the plan cost calculation coefficient of the planner, which increases the probability that the generic or custom plan will be selected more often.
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 a segmentation fault, which occurred during
SELECTqueries and was caused by an oversight in the previous bugfix related to self join removal optimization.Fixed an outdated recommendation to customize a unit file in the
postgrespro-std-14.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.11.2. Migration to Version 14.9.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 toPostgres Pro versions starting with 14.8.1, make sure to upgradepg_probackup to version 2.6.3 or higher since lower versions are incompatible with thesePostgres Pro versions.
To migrate fromPostgreSQL or aPostgres Pro Standard release based on a previousPostgreSQL major version, see the instructions inPostgres Pro Standard 14.1.1 Release Notes.