This is expected to be the last Postgres Pro Standard release in the 9.6 series. Users are encouraged to update to a newer Postgres Pro Standard major version soon.
This release is based on PostgreSQL 9.6.24 and Postgres Pro Standard 18.104.22.168. All improvements inherited from PostgreSQL 9.6.24 are listed in PostgreSQL 9.6.24 Release Notes. Other major changes and enhancements are as follows:
Dropped support for the sr_plan extension.
Upgraded mamonsu to version 3.1.0. Notable changes are as follows:
A new option for
bootstrapis added. With this option, if
-dbnameis not explicitly specified, its value will be automatically set to the database name defined in the
[postgres]section of the mamonsu configuration file.
A critical issue is fixed that could arise when the
bootstrapstep was skipped. In this case, although a user can work with mamonsu under superuser permissions, the special
mamonsuschema is not created, but after creating the auxiliary extension pg_buffercache in any other schema, running mamonsu resulted in errors “
ERROR: relation "mamonsu.pg_buffercache" does not exist...”.
Fixed a pg_probackup issue with archiving WAL from a directory outside of the data directory. Previously, multi-threaded and batch optimizations of
archive-pushprevented such archiving; now it is possible to archive WAL from any directory, but if it is outside of the data directory, multi-threaded and batch optimizations are automatically turned off.
Migration to Version 22.214.171.124
Depending on your current installation, the upgrade procedure will differ.
To upgrade from a Postgres Pro Standard version based on any previous PostgreSQL major release, make sure you have installed its latest minor version, and then perform a dump/restore using pg_dumpall or use the pg_upgrade utility.
To upgrade from a Postgres Pro Standard version based on the same PostgreSQL major release, a dump/restore is not required.
numeric_le are actually leakproof, they were not marked as such in Postgres Pro Standard 126.96.36.199 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 188.8.131.52 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
Since pg_probackup delivery model changed in Postgres Pro Standard 184.108.40.206, 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 220.127.116.11 or lower, you must call the
REINDEX command for indexes that used
If you are upgrading from Postgres Pro Standard 18.104.22.168 or lower, you must also use the pgpro_upgrade script provided in this distribution. This script updates metadata information to handle catalog number format change introduced after Postgres Pro Standard 22.214.171.124, as well as rename the
pgpro_build function to
pgpro_upgrade script is usually run automatically. However, if you have created your database in a non-default location, you must run the
pgpro_upgrade script manually.
If you run
pgpro_upgrade manually, you must stop postgres service. The script must be run on behalf of the user owning the database (typically postgres). Running
pgpro_upgrade as root will result in an error. For details, see pgpro_upgrade.
On RPM-based Linux distributions, if you are upgrading from version 126.96.36.199 or lower, make sure to move the data directory from
pgsql to the
pgpro directory before running the
To migrate from vanilla PostgreSQL 9.6.x, make sure you have installed its latest available minor version and then perform a dump/restore using pg_dumpall.