Added the generic_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 the enable_appendorpath configuration parameter, which enables the Append plan for OR clauses. It is useful for applications with auto-generated queries.

Fixed logical replication to a Postgres Pro Enterprise server from servers of different editions: PostgreSQL or Postgres Pro Standard of the same or a previous version.

Fixed a segmentation fault, which occurred during SELECT queries and was caused by an oversight in the previous bugfix related to self join removal optimization.

Fixed an issue with calculating the page base for 64-bit XIDs. In some rare cases, it could lead to a transaction failure or to an incorrect xmin, which manifested itself in errors, such as “Fatal xid base calculation error”.

Fixed an issue that could cause the pg_database_size function to return incorrect database size, which was different from the actual disk space, when using the CFS. Previously, the size of CFS sparse files was calculated using the logical file size rather than the physical file size in data blocks.

Fixed states of non-CFS background workers displayed in the pg_stat_activity view. The worker status is now set correctly after garbage collection.

Fixed an issue in pgpro_scheduler with supervisor scheduler removing the database manager data before its initialization, which could lead to the manager exiting with an error “Scheduler manager XX: cannot find information about self in scheduler_state”.

Added support for Debian 12 and ended support for Debian 9.

Fixed an outdated recommendation to customize a unit file in the postgrespro-ent-14.service file 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 joinsel component, which is needed for a more accurate cardinality estimation by several columns. If for some reason (for example, because of insufficient detailed statistics) joinsel cannot make a good prediction, Postgres Pro will not use joinsel in this particular case, but estimate cardinality using a regular algorithm. If joinsel has 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, mvarchar types larger than 250 MB. Now up to 1 GB of data of these types can be stored correctly.

Upgraded pg_probackup to version 2.6.5 Enterprise, which provides the following optimizations and bug fixes:

Upgraded pg_hint_plan to include a bugfix related to hint stack corruption.

Upgraded pgpro_pwr to version 4.2, which adds interactive features to the report.

Upgraded PTRACK to version 2.5 Enterprise.