Release date: 2020-08-24
This release is based on PostgreSQL 9.6.19 and Postgres Pro Enterprise 9.6.18.1. All improvements inherited from PostgreSQL 9.6.19 are listed in PostgreSQL 9.6.19 Release Notes. As compared with Postgres Pro Enterprise 9.6.18.1, this version also provides the following changes:
Improved the rum extension:
Improved full text search for tsvector values 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.
Fixed bug in pgpro_scheduler that prevented stopping of the running
jobs on schedule.stop().
Fixed the GUC parameter group naming. A
Compressed File System parameter 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-push and set-backup commands.
Incremental restore and support for multi-timeline incremental chains have been added.
Postgres Pro parameters slot_name and primary_conninfo can be used during restore.
archive-push and archive-get commands 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.
Depending on your current installation, the upgrade procedure will differ.
To migrate from vanilla PostgreSQL 9.6.x or Postgres Pro Standard,
make sure you have installed its latest minor version and then perform a dump/restore using pg_dumpall.
Besides, make sure to pay special attention to implementation specifics of
64-bit transaction IDs. If
you have used explicit casts to 32-bit integers when handling transaction
IDs, you have to replace them with casts to bigint since
64-bit transaction IDs are of the bigint type.
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 9.6.16.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 9.6.17.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 VOLATILE
To upgrade from a Postgres Pro Enterprise version
based on the same PostgreSQL major release,
a dump/restore is not required.
It is usually enough to install the new version into the same installation directory.
Once the new binaries are installed, the pgpro_upgrade
script is run automatically to check whether additional setup is required
and complete the upgrade.
Since pg_probackup delivery model changed in
Postgres Pro Enterprise 9.6.12.1, when upgrading from
a lower version on ALT Linux and Debian-based systems, run
apt dist-upgrade (or apt-get dist-upgrade)
to ensure that all new dependencies are handled correctly. On Windows,
you have to run a separate pg_probackup
installer to complete the upgrade.
When upgrading from versions 9.6.9.1 through 9.6.14.1, 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 9.6.8.2 or lower, you have to rebuild indexes
that used mchar or mvarchar types.
When upgrading from versions 9.6.2.1 or lower, you have to rebuild
GiST indexes built over columns of the intarray type.
When upgrading from version 9.6.1.2 on RPM-based
Linux distributions, make sure to move the data directory from
pgsql to the pgproee
directory before running the pgpro_upgrade script.
For some Linux distributions, you may be prompted to run pgpro_upgrade manually.
In this case, you must stop the postgres service.
The script must be run on behalf of the user owning the database
(typically postgres) and PGDATA environment variable should be
set to the directory where database resides. Running pgpro_upgrade
as root will result in an error.
This step is not required when upgrading from version 9.6.4.1 or higher.