E.2. Postgres Pro Standard

Release date: 2020-11-20

E.2.1. Overview

This release is based on PostgreSQL 9.6.20 and Postgres Pro Standard All improvements inherited from PostgreSQL 9.6.20 are listed in PostgreSQL 9.6.20 Release Notes. Other major changes and enhancements are as follows:

  • Ended support for Red Hat Enterprise Linux (RHEL) 6 and its derivatives: Oracle Linux 6 and 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.

  • Fixed the pgpro_upgrade script, which did not behave as described in the documentation on Debian-based operating systems. There, the script previously ignored the -D/--pgdata option, to be used to specify the data directory, and the --check option did not produce the documented output.

  • Upgraded mamonsu to version 2.6.1.

  • Upgraded pgbouncer to version 1.15.

E.2.2. Migration to Version

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.

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 Standard 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 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, 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 or lower, you must call the REINDEX command for indexes that used mchar or mvarchar types.

If you are upgrading from Postgres Pro Standard 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, as well as rename the pgpro_build function to pgpro_source_id. The 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 or lower, make sure to move the data directory from pgsql to the pgpro directory before running the pgpro_upgrade script.

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.