E.14. Postgres Pro Enterprise 10.15.1
Release date: 2020-11-27
E.14.1. Overview
This release is based on PostgreSQL 10.15 and Postgres Pro Enterprise 10.14.1. All changes inherited from PostgreSQL 10.15 are listed in PostgreSQL 10.15 Release Notes. Other major changes and enhancements are as follows:
Ended support for CentOS 6.
Fixed a bug in the pg_variables module. Now you can create a variable in a transaction after removal of a variable with the same name.
Upgraded mamonsu to version 2.6.2.
Upgraded pgbouncer to version 1.15.
Improved the precision of pgbench when the
--default-isolation-leveloption is used. The default isolation level is now set in the environment variablePGOPTIONSso that TPS values are computed consistently, with or without the--connectoption.Fixed CFS to dramatically speed up pg_basebackup for a database that contains a lot of small tables. Previously, nearly 1 MB of zeroes was produced for each relation to be copied.
Updated pgpro_scheduler:
Now pgpro_scheduler waits in the suspended state on a standby server to be started when the standby is promoted to a master server. Previously it didn't work on a standby server either and besides generated a lot of error messages.
Enhanced the scheduling scale used by pgpro_scheduler — jobs can now be scheduled to a precision of seconds. Also some predefined keywords can now be used instead of
crontabstrings.
The use of pg_upgrade for upgrading a PostgreSQL or Postgres Pro Standard instance to Postgres Pro Enterprise 10 is no longer supported. If you need to upgrade from these versions, use a dump/restore.
E.14.2. Migration to Version 10.15.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.
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.