Release date: 2021-12-07
This release is based on PostgreSQL 10.19 and Postgres Pro Enterprise 10.18.1. All changes inherited from PostgreSQL 10.19 are listed in PostgreSQL 10.19 Release Notes. Other major changes and enhancements are as follows:
Fixed pg_dump to handle 64-bit XID statistics correctly, which is important when upgrading Postgres Pro Enterprise using pg_upgrade. Previously, values over 232 in XID statistics were incorrectly transferred, which led to the launch of autovacuum to prevent transaction ID wraparound.
Fixed an issue with an upgrade of Postgres Pro Enterprise 9.6 cluster to the current major version using pg_upgrade. Previously, it incorrectly converted free space maps of tables larger than 4 TB.
Dropped support for the sr_plan extension.
Upgraded mamonsu to version 3.1.0. Notable changes are as follows:
A new option for bootstrap is added. With this option,
if -dbname is not explicitly specified, its value will be automatically set to the
database name defined in the [postgres] section of the mamonsu
configuration file.
A critical issue is fixed that could arise when the bootstrap step was skipped.
In this case, although a user can work with mamonsu under superuser permissions,
the special mamonsu schema is not created, but
after creating the auxiliary extension pg_buffercache
in any other schema, running mamonsu resulted in errors
“ERROR: relation "mamonsu.pg_buffercache" does not exist...”.
Forbade access to temporary namespaces from autonomous transactions to ensure predictable behavior.
Enforced the size limit of 16TB to non-system tables with non-unique and not covering B-tree indexes to avoid issues with such indexes in extremely large tables.
Fixed a pg_probackup issue with archiving WAL from a
directory outside of the data directory. Previously, multi-threaded and batch optimizations of archive-push
prevented such archiving; now it is possible to archive WAL from any directory, but if it is outside of the data directory,
multi-threaded and batch optimizations are automatically turned off.
Fixed pg_dumpall to avoid using an insecure search path.
Deprecated WAITLSN command.
Leveraged sparse file functionality in Windows for CFS,
which optimizes on-disk size of *.cfm files, up to 1MB each.
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.