E.6. Postgres Pro Enterprise 12.3.1

Release date: 2020-05-29

E.6.1. Overview

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

  • Fixed an issue with an infinite loop that could lead to consuming all the available memory while planning join operations with multiple IN conditions.

  • Fixed an issue that could lead to server failure if autovacuum tried to access a manually dropped temporary namespace.

  • Fixed an issue that could lead to losing transactional consistency if multiple autonomous transactions were in use.

  • Fixed an issue with the SHOW command that could previously display incorrect parameter values if built-in connection pooling was enabled.

  • Fixed the default value of the plan_cache_lru_size parameter. Instead of 64, now it is really set to zero, which means there is no limit on the number of prepared statements that can be kept in memory, so the size limit enforced by plan_cache_lru_memsize takes effect.

  • Fixed incorrect memory access in implementation of deduplication for B-tree indexes to avoid potential issues during recovery.

  • Added the -c/--restore-target-wal option for pg_rewind to automatically retrieve missing WAL files from WAL archive using the restore_command defined in the target cluster configuration. This Postgres Pro feature has been accepted by the PostgreSQL community and is targeted to appear in vanilla PostgreSQL 13.

  • Enabled index replacement for primary key and exclusion constraints using the ALTER CONSTRAINT ... USING INDEX clause of the ALTER TABLE command; previously, this functionality was supported only for unique constraints. Besides, index compatibility checks performed during such replacements have been refined.

  • Updated CFS to allow changing the cfs_gc_threshold parameter for the current session. Now you can temporarily set it to a smaller value if you would like to manually defragment a relation with a smaller percent of garbage than is currently allowed.

  • Fixed a memory leak that could occur during join operations if they required estimating multiple query execution paths for complex queries.

  • Added the --no-data-checksums option for initdb to allow initializing Postgres Pro clusters with checksums disabled.

  • Optimized writing of empty pages to *.cfm files in base backups.

  • Added support for Oracle Linux 8.

  • Added support for ALT Linux 8 SP.

  • Added support for Ubuntu 20.04.

  • Added the plpython3 package for Rosa Enterprise Linux Server 7, ROSA COBALT (server edition) based on Rosa platform 7, and AlterOS 7.5 distributions where it was previously missing. Now it is available on all supported platforms except SLES 11.

  • Upgraded several libraries provided with Postgres Pro on Windows. Now the following libraries are used: OpenSSL 1.1.1g, libzstd 1.4.4, gettext 0.20.2, libiconv 1.16, libxml2 2.9.9, and libxslt 1.1.32. The ICU library has been upgraded from version 56.1 to 56.2.

  • Upgraded PTRACK extension to version 2.1. In the new version, the API has been significantly reworked. In particular, you now have to set the ptrack.map_size parameter instead of ptrack_map_size to enable this feature. See PTRACK documentation for details.

  • Updated the multimaster extension. Now it provides the mtm.check_query(query_text) function for checking data consistency between cluster nodes. For details, see Section F.30.4.6.

  • Upgraded pgpro_scheduler to version 2.6. This version introduces several enhancements, including a full rework of cron parser implementation. Besides, pgpro_scheduler now starts scheduled jobs once a background worker becomes available if there were not enough workers to start the job on time.

  • Upgraded pageinspect to version 1.6 to correctly handle 64-bit transaction IDs.

  • Updated vops to provide an automated way of generating and accessing vectorized data. For details, see Section F.70.5.5.

  • Upgraded pg_pathman to version 1.5.11 to avoid server failure when trying to access child partitions without the required permissions while parent table access is allowed. This issue could previously occur when using pg_pathman with Postgres Pro 11.7.1 or higher.

E.6.2. Migration to Version 12.3.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.

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.