E.11. Postgres Pro Enterprise 15.4.1
Release Date: 2023-08-24
E.11.1. Overview
This release is based on PostgreSQL 15.4 and Postgres Pro Enterprise 15.3.1. All changes inherited from PostgreSQL 15.4 are listed in PostgreSQL 15.4 Release Notes. As compared with Postgres Pro Enterprise 15.3.1, this version also provides the following changes:
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 forOR
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-15.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 usejoinsel
in this particular case, but estimate cardinality using a regular algorithm. Ifjoinsel
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.Added two alternative views called
V$SESSION
andV$SESSION_LONGOPS
, which are familiar to Oracle users, in the pgpro_application_info extension.Upgraded pg_probackup to version 2.6.5 Enterprise, which provides the following optimizations and bug fixes:
An attempt of a partial restore to a non-empty
PGDATA
directory now completes with an error, but a possibility of such a restore is retained with the--destroy-all-other-dbs
flag 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 show
commandRestore from backups with the
--recovery-target-timeline
and--no-validate
options
Improved processing of files in compressed tablespaces by the PTRACK module.
Renamed the
--skip-if-exist
flag to--skip-if-exists
.
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.
Added two new functions in the sr_plan extension:
sr_plan_unfreeze
, which removes a query execution plan only from the file storage and keeps a query registered in local cache, andsr_unregister_query
, which removes a registered query from the local cache.
E.11.2. Migration to Version 15.4.1
If you are upgrading from a Postgres Pro Enterprise release based on the same PostgreSQL major version, it is enough to install the new version into your current installation directory.
When upgrading to Postgres Pro Enterprise versions starting with 15.3.1, make sure to upgrade pg_probackup Enterprise to version 2.6.4 or higher since lower versions are incompatible with these Postgres Pro Enterprise versions.
To migrate from PostgreSQL, as well as Postgres Pro Standard or Postgres Pro Enterprise based on a previous PostgreSQL major version, see the migration instructions for version 15.