Postgres Pro
Downloads
E.7. Postgres Pro Enterprise 12.16.1
Prev UpAppendix E. Release NotesHome Next

E.7. Postgres Pro Enterprise 12.16.1

E.7.1. Overview
E.7.2. Migration to Version 12.16.1

Release date: 2023-08-21

E.7.1. Overview

This release is based on PostgreSQL 12.16 and Postgres Pro Enterprise 12.15.1. All changes inherited from PostgreSQL 12.16 are listed in PostgreSQL 12.16 Release Notes. As compared with Postgres Pro Enterprise 12.15.1, this version also provides the following changes:

  • Added the enable_appendorpath configuration parameter, which enables the Append plan for OR clauses. It is useful for applications with auto-generated queries.

  • 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-12.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:

    • 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 command

      • Restore 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 version 1.3.8 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.

E.7.2. Migration to Version 12.16.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.

If you are migrating to the current major version of Postgres Pro Enterprise using pg_upgrade, and you want to keep the existing visibility map representation in pageinspect, you should run the VACUUM command before the upgrade.

If you have previously migrated to Postgres Pro Enterprise 12.7.1 or lower, you must run the REINDEX command to rebuild GIN indexes.

If you have previously migrated from Postgres Pro Enterprise versions 11 or 10, you must run the REINDEX command to rebuild B-tree indexes, except for unique, covering and system indexes. If you are migrating from these versions now, rebuilding such indexes is also recommended.

If you are upgrading from Postgres Pro Enterprise versions 12.6.x or lower and take PTRACK backups using pg_probackup, retake a full backup after upgrade.

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 12.

Prev Up Next
E.6. Postgres Pro Enterprise 12.16.2 Home E.8. Postgres Pro Enterprise 12.15.1
epub pdf