Release date: 2020-02-26
This release is based on PostgreSQL 10.12 and Postgres Pro Enterprise 10.11.1. All changes inherited from PostgreSQL 10.12 are listed in PostgreSQL 10.12 Release Notes. Other major changes and enhancements are as follows:
Increased the maximum value of the track_activity_query_size parameter to 1MB. In vanilla PostgreSQL, this change is targeted for version 13.
Fixed planner's optimization to correctly take into account
similar OR clauses if they reference
columns that are different, but have the same position
in different indexes.
Updated CFS to enhance compression functionality:
The cfs_compress_small_relations parameter
controls whether small tables are compressed. It may be useful to
turn off this setting for databases with many relations smaller than
1GB to avoid overhead.
Fixed the mchar extension to
correctly handle the ESCAPE clause in
SIMILAR TO regular expressions.
Improved query performance with row-level security policy enabled by correctly marking numeric comparison functions as leakproof.
Upgraded pg_probackup to version 2.2.7.
Upgraded mamonsu to version 2.4.4.
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.