Release date: 2019-02-21
This release is based on PostgreSQL 9.6.17 and Postgres Pro Enterprise 9.6.16.1. All improvements inherited from PostgreSQL 9.6.17 are listed in PostgreSQL 9.6.17 Release Notes. As compared with Postgres Pro Enterprise 9.6.16.1, this version also provides the following changes:
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.
Improved query performance with row-level security policy enabled by correctly marking numeric comparison functions as leakproof.
Fixed the mchar extension to correctly handle the
ESCAPE clause in SIMILAR TO
regular expressions.
Upgraded pg_probackup to version 2.2.7.
Upgraded mamonsu to version 2.4.4.
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.
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 version 9.6.9.1 or lower, you must run the
REINDEX command to rebuild GiST and SP-GiST indexes.
When upgrading from version 9.6.8.2 or lower,
you must run the REINDEX command for indexes that used
mchar or mvarchar types.
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.