E.15. Postgres Pro Enterprise 10.14.1
Release date: 2020-08-25
E.15.1. Overview
This release is based on PostgreSQL 10.14 and Postgres Pro Enterprise 10.13.1. All changes inherited from PostgreSQL 10.14 are listed in PostgreSQL 10.14 Release Notes. Other major changes and enhancements are as follows:
Disabling password reuse now correctly works with SCRAM authentication. Previously SCRAM-encrypted password was reused even when it was not supposed to.
Improved the rum extension:
Improved full text search for
tsvectorvalues with the lexeme weights specified. When executing queries with the weight-based constraints, the index search results do not need to be rechecked in table, so these queries perform much faster.Fixed the error which causes result loss when the negation operator is used in such queries.
Added the optional
tuneargument to thepg-setup initdbcommand. This argument allows you to choose one of the predefined customized configurations for your database cluster.Fixed bug in pgpro_scheduler that prevented stopping of the running jobs on
schedule.stop().Fixed the GUC parameter group naming. A
Compressed File Systemparameter group name has been omitted previously which caused other group names to be shifted.Ended support for SUSE Linux Enterprise Server 11.
Fixed race conditions in BRIN index that caused errors:
"failed to find parent tuple for heap-only tuple ...".
The error could occur when the
brin_summarize_new_values()function and HOT updates were executed simultaneously in concurrent transactions."corrupted BRIN index: inconsistent range map".
The error could occur when BRIN index's desummarization and a bitmap scan were executed simultaneously in concurrent transactions.
Upgraded pg_probackup to latest version 2.4.2:
New options and flags can now be used to add flexibility to
delete,backup,restore,archive-pushandset-backupcommands.Incremental restore and support for multi-timeline incremental chains have been added.
Postgres Pro parameters
slot_nameandprimary_conninfocan be used during restore.archive-pushandarchive-getcommands considerably reworked.Improvements have been achieved in speed and memory consumption.
See pg_probackup documentation for details.
Upgraded mamonsu for Linux systems to version 2.5.1. Now it is based on Python 3. Version 2.3.4 is still provided for Windows systems.
E.15.2. Migration to Version 10.14.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.