Release date: 2022-09-01
This release is based on PostgreSQL 10.22 and Postgres Pro Enterprise 10.21.1. All changes inherited from PostgreSQL 10.22 are listed in PostgreSQL 10.22 Release Notes. Other major changes and enhancements are as follows:
Fixed an issue with a large number of warnings issued during page conversion
after the upgrade of Postgres Pro Enterprise 9.6
cluster to the current major version. Now pd_prune_xid values
of version-9.6 pages are reset to zero.
Fixed a bug in the logic of epoch shifting, which didn't take into account the
XMAX_INVALID hint bit of the tuple. Previously, it could lead
to a sudden increase of the current transaction ID.
Upgraded mamonsu to version 3.5.1. Notable changes are as follows:
Resolved the security issue of exposing passwords through the configuration
file. Only mamonsu user can access agent.conf now.
Fixed metrics computation that caused “float division by zero” errors in the mamonsu STATEMENTS plugin.
Upgraded pg_probackup to version 2.5.7, which provides the following new features and bugfixes:
Enabled output of logs in the JSON format by adding new logging options.
Added an option to explicitly specify the directory where the restore
command should restore WAL records.
Changed the level of detail of logging some messages of pg_probackup commands to add user convenience to reading logs.
Fixed pg_probackup hanging that could occur when the
ControlMaster option was specified in the SSH
config file. Now the value of ControlMaster is
explicitly set to “no”.
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 10.17.1 or lower, you must run the
REINDEX command to rebuild GIN indexes.
While functions numeric_eq,
numeric_ne, numeric_gt,
numeric_ge, numeric_lt,
and numeric_le are actually leakproof, they were not
marked as such in Postgres Pro Enterprise 10.11.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 10.12.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
Starting from Postgres Pro Enterprise 10.11.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.
When upgrading from versions 10.6.2 or lower, you must run the
REINDEX command to rebuild GIN, GiST, and SP-GiST indexes
to fix replication issues that could be observed in these versions.
You should also retake all backups for these versions if your database had such indexes.
When upgrading from versions 10.3.3 or lower,
you have to rebuild GiST indexes built over columns of the
intarray type, as well as indexes that use
mchar or mvarchar types.
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 10.
If you are opting for a dump/restore, make sure to use the --add-collprovider
option to correctly choose the provider for the default collation of the migrated database.