Release date: 2021-03-01
This release is based on PostgreSQL 10.16 and Postgres Pro Enterprise 10.15.1. All changes inherited from PostgreSQL 10.16 are listed in PostgreSQL 10.16 Release Notes. Other major changes and enhancements are as follows:
Deprecated the cfs_compress_small_relations parameter.
Small relations are still compressed by default and will not differ
from the bigger ones. Make sure to keep the existing parameter setting intact
for the lifetime of your database cluster.
Fixed a bug in the CFS implementation that resulted in disabling compression
for all relations when the cfs_compress_temp_relations parameter was set.
Added the pg_snapshot_any function to help superusers explore corrupted
databases. See Section 9.26.11 for details.
Aligned the behavior of the parameters idle_session_timeout and
idle_in_transaction_session_timeout with how they will
behave in a future PostgreSQL release. Specifically,
the idle_session_timeout parameter now applies
only when outside a transaction.
Upgraded pg_probackup to the latest version 2.4.10. Major improvements over the previously included version 2.4.2 are as follows:
Incremental restore with --force flag now allows you to overwrite the contents of the directory
specified by PGDATA in case of system ID mismatch.
Previously this resulted in an error.
It is now possible to restore and validate backups from a read-only filesystem.
In-place merge is now disabled only if the storage format changed.
Non-exclusive backup locks are implemented, which enables concurrent validate and restore. Backup shared locks are now released at the process exit.
Streamed WAL segments are now added to the backup filelist on the fly and fsynced to disk at the end of the backup.
See pg_probackup documentation for details.
Fixed a bug in pgpro_scheduler due to which jobs scheduled to run exactly at the start of an hour (but at a two-hour or larger interval) were not executed at all.
Added pgpro_controldata utility to display control information of a PostgreSQL/Postgres Pro database cluster and compatibility information for a cluster and/or server.
Fixed the behavior of pg_wait_sampling
in case of interrupting a client backend that accessed the shared queue.
Previously, the pg_wait_sampling collector could hang in such cases
and block other backends trying to read the pg_wait_sampling_profile view.
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.
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.