E.20. Postgres Pro Enterprise 13.6.1

Release Date: 2022-03-18

E.20.1. Overview

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

  • Improved access to the LSN field in the page header by reading it atomically instead of locking to reduce lock contention; added caching of the block number of the page to speed up retrieving of block numbers. Now multiple clients can provide better performance when accessing the same blocks concurrently.

  • Added the pgpro_stats_wal_sender_crc_errors function that returns the number of errors detected by the WAL sender process.

  • Increased the number of partitions of the shared buffer mapping hash table to 1024, which can improve performance on multi-core systems.

  • Implemented support of interval values by all time parameters (*_TIME) of CREATE PROFILE and ALTER PROFILE SQL commands.

  • Fixed a bug in the CFS causing subtle corruption of data in compressed tablespaces at the server startup on Windows after an abnormal termination or when restoring a backup.

  • Fixed an issue with lazy conversion from 32-bit to 64-bit transaction IDs in read-only transactions or on replicas by enforcing marking pages as subject to full-page writes to WAL. This issue could cause failures to synchronize conversion results to other replicas.

  • Fixed segmentation fault, which might have occurred when executing a specific procedure calling pattern while plan_cache_lru_memsize was set.

  • Fixed an issue with *.cfm files that were unexpectedly left in compressed tablespaces after dropping a table.

  • Fixed VACUUM logic for handling multixact IDs correctly. Previously, table vacuuming could produce found multixact XXX from before relminmxid... errors, which didn't corrupt data.

  • Fixed the use of multi-column statistics by planner. Previously, when the optimizer estimated the query selectivity using multi-column statistics and the query conditions only included part of the columns involved, the cardinality could be considerably overestimated, so the created plan would be non-optimal.

  • Fixed the out-of-memory (OOM) killer settings in system startup files. Previously the OOM score adjustment value was set for all Postgres Pro processes rather than for postmaster only, so when Postgres Pro exhausted all RAM, the OOM killer could start killing irrelevant processes, such as sshd.

  • Fixed an issue in psql, which mistakenly treated the \du+ meta-command as invalid. \du+ lists database roles showing additional information about each role and is equivalent to the \dg+ meta-command, which was processed correctly.

  • Added support for Rocky Linux 8.

  • Ended support for outdated operating systems Debian 8, Astra Linux Smolensk 1.5 and MSVSphere 6.3.

  • Upgraded mamonsu to version 3.4.0. Notable changes are as follows:

    • Added a new timeout parameter to the [zabbix] section of the mamonsu configuration file. It allows you to set maximum time to wait while connecting to the Zabbix server.

    • Added a new mamonsu dashboard upload template_name command, which can be used to upload a Zabbix dashboard with the mamonsu metrics to a template on the Zabbix server version 6.0 or higher.

  • Fixed an issue with disconnecting nodes in multimaster by disabling timeouts for the multimaster processes. Previously, the processes could abort due to timeouts set in the server configuration, e.g. statement_timeout.

  • Added the --checkunique option to the pg_probackup checkdb command to work together with --amcheck and verify unique constraints during logical verification of indexes when the amcheck extension is installed in the database and its version supports this verification. Check with the documentation for amcheck for more details.

  • Upgraded pgpro_pwr to version 3.7.

E.20.2. Migration to Version 13.6.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 have previously migrated to Postgres Pro Enterprise 13.3.1 or lower, you must run the REINDEX command to rebuild GIN indexes.

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

If you have an installation of Postgres Pro Enterprise 13.2.1 that contains compressed tablespaces created without explicitly specifying the pglz algorithm, perform an upgrade as follows. Before upgrading, make a complete dump using pg_dumpall. Upgrade Postgres Pro Enterprise, re-create your database cluster, and restore the dump. Then you can create compressed tablespaces in the same way as before.

If you have already upgraded your installation with CFS tablespaces from Postgres Pro Enterprise 13.2.1, and you cannot access the compressed data, call the support team.

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