E.9. Postgres Pro Enterprise 12.14.1
Release date: 2023-03-03
E.9.1. Overview
This release is based on PostgreSQL 12.14 and Postgres Pro Enterprise 12.13.2. All changes inherited from PostgreSQL 12.14 are listed in PostgreSQL 12.14 Release Notes. As compared with Postgres Pro Enterprise 12.13.2, this version also provides the following changes:
Fixed a segmentation fault, which might have occurred in PL/pgSQL when trying to remove a separate field of a composite type upon completion of an autonomous transaction.
Added support for ROSA COBALT Server 7.9 and ended support for ROSA COBALT Server 7.3.
Fixed suboptimal memory usage in optimizing a query that included a pretty large number of
UNION ALLsubqueries. This planner issue was due to a vanilla PostgreSQL issue with replacing placeholder variables in a special case of flatteningUNION ALLleaf queries.Upgraded pg_probackup to version 2.6.1 Enterprise, which provides the following features:
Optimized pg_probackup input/output engine to improve performance.
Added Simple Storage Service (S3) support for storing data in private clouds. S3 interface was tested with MinIO object storage and VK Cloud storage. Note that pg_probackup provides complete processing of S3 interface logging.
Added CFS (Compressed File System) support for incremental backups in
DELTA,PAGE, andPTRACKmodes.PTRACKmode requires PTRACK 2.4.0 or higher and is recommended as the fastest mode for incremental backups.Added support for zstd compression algorithm.
Ended support for Postgres Pro 9.6.
Upgraded PTRACK to version 2.4.1.
Upgraded pgbouncer to version 1.18.
Upgraded pgpro_scheduler to version 2.9, which provides the following changes:
Fixed the
schedule.resubmitfunction to save the state of the executed job correctly. Also, this function can now accept 0 as the time interval, in this case the job is resubmmitted immediately after execution.Fixed an issue with the
schedule.timetablefunction, which previously caused an error when the function was called by any superuser other thanpostgres.
Updraded pgpro_stats to version 1.5, which provides new features and bugfixes:
Added computation of statistics on removal of all-frozen and all-visible marks in the visibility map.
Added the
pgpro_stats_vacuum_databaseview, showing statistics about vacuuming each database in a cluster.Fixed possible crash of a server where
pgpro_stats.trackwas set toallthat could occur when pgpro_stats processed a function body as a multistatement query.Fixed inappropriate issuing of an “unrecognized expression node type: ...” warning in case a query plan contained a GatherMerge node.
Fixed too long execution of a query containing texts of JSON or XML documents of a special kind. The slowdown was possible because normalization of the query plan text could mistakenly include replacement of constants inside those documents.
Upgraded pgpro_pwr to version 4.1.2.
E.9.2. Migration to Version 12.14.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.