E.4. Postgres Pro Enterprise 11.18.1
Release date: 2022-12-02
This release is based on PostgreSQL 11.18 and Postgres Pro Enterprise 11.17.2. All changes inherited from PostgreSQL 11.18 are listed in PostgreSQL 11.18 Release Notes. As compared with Postgres Pro Enterprise 11.17.2, this version also provides the following changes:
Added slru_buffers_size_scale that allows to scale the size of SLRU shared memory buffers. Note that the buffer sizes changed due to this improvement.
Fixed compatibility of Section F.22 with autonomous transactions.
Fixed a segmentation fault in postgres_fdw, which might have occurred when a query was canceled.
Improved garbage collection logic. Now percent of garbage is calculated based on file size rounded to 4 kB (typical filesystem block size) instead of raw file size, which prevents frequent defragmentation of small files.
Fixed an issue with physical replication, which could lead to a replica crash in rare cases. Previously, WAL records on update and init of heap pages did not contain
xmaxvalues could be set.
Fixed huge selectivity overestimation observed in rare cases, which could result in a sequential scan of a whole relation instead of a quick index scan, so certain queries were executed much more slowly than expected. The issue was due to an oversight in a recent optimization of selectivity estimation.
Upgraded mamonsu to version 3.5.2, which provides new features and bugfixes. Notable changes are as follows:
Added autovacuum utilization metrics.
Added Zabbix macros based on plugin parameters from the configuration file, so that triggers can now be dynamically changed directly in Zabbix without updating the configuration file and restarting mamonsu.
Upgraded pg_probackup to version 2.5.10, which provides optimizations and bugfixes. Notable changes are as follows:
*.cfmfiles backup by truncating trailing zeroes.
Fixed an issue with
--amcheck, which previously completed with an error when the checked database contained partitioned indexes.
Fixed a backup failure on a replica that occurred because the version of the pg_probackup agent running there was different from that on the master.
Upgraded pgpro_scheduler to version 2.8. This version introduces the schedule.timetable() function, which returns all the jobs, both scheduled and one-time, within the specified time interval.
E.4.2. Migration to Version 11.18.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.
Migration of a cluster with tables larger than 16Tb to Postgres Pro Enterprise versions 11 or 10 is not supported.
If you have previously migrated to Postgres Pro Enterprise 11.12.1 or lower, you must run the
REINDEX command to rebuild GIN indexes.
numeric_le are actually leakproof, they were not marked as such in Postgres Pro Enterprise 11.6.1 or lower, which could lead to incorrect query optimization. In particular, it negatively affected query execution if row-level security policy was in use. Version 11.7.1 repairs this issue for new installations by correcting the initial catalog data, but existing installations will still have incorrect markings unless you update
pg_proc entries for these functions. You can run pg_upgrade to upgrade your server instance to a version containing the corrected initial data, or manually correct these entries in each database of the installation using the
ALTER FUNCTION command. For example:
ALTER FUNCTION pg_catalog.numeric_eq LEAKPROOF
Version 11.7.1 also fixes
SIMILAR TO and POSIX regular expressions that use character classes for icu collations, so you may need to check for objects that use such regular expressions.
Starting from Postgres Pro Enterprise 11.6.1, the ICU library upgrade does not interfere with the server start. Before connecting to a database using ICU as the default collation, Postgres Pro compares this collation version to the one provided by the ICU library and displays a warning if the collation versions do not match; you may need to rebuild the objects that depend on the default collation if you think the collation change may affect the sort order of your data. To suppress these warnings, you can use the
ALTER COLLATION "default" REFRESH VERSION command, as explained in ALTER COLLATION.
If you are upgrading from Postgres Pro Enterprise versions 11.11.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 11.