E.6. Postgres Pro 126.96.36.199
Release date: 2019-03-05
This release is based on PostgreSQL 9.5.16 and Postgres Pro Standard 188.8.131.52. All improvements inherited from PostgreSQL 9.5.16 are listed in PostgreSQL 9.5.16 Release Notes.
Major enhancements over Postgres Pro Standard 184.108.40.206 include:
Changed the default authentication method for installations on SUSE Linux Enterprise Server systems, as well as Red Hat Enterprise Linux 7 and its derivatives. Now local connections use the
peermethod, while network connections use
md5. For details on supported authentication methods, see Section 19.3.
Backported the patch that addresses
dsm_attach()race condition when DSM handles are reused; in vanilla PostgreSQL, this fix is targeted for the future updates only. The patch is hoped to resolve issues when the server reports the following error message:
ERROR: dsa_area could not attach to segment.
Ended support for ALT Linux SPT 6.0 and Windows 7 SP1.
pg_pathmanmodule to version 1.5.5. As compared to version 1.5.2 provided in the previous Postgres Pro releases, the following enhancements were introduced:
pg_pathmanupgrade scripts to avoid issues caused by a different the number of
pg_pathman1.4 and 1.5 major versions.
Trying to call
pg_pathmanfunctions when this extension is disabled does not cause server failures anymore; now an error is raised instead.
Different partitioning strategies can now be successfully applied to the same table.
pg_variablesmodule to version 1.2. As compared to the version provided in the previous Postgres Pro releases, the following enhancements were introduced:
Added support for array types.
Improved module stability.
Changed empty package handling. An empty package is now removed only after the transaction that emptied it has ended.
(See Section F.37.)
E.6.2. Migration to Version 220.127.116.11
Depending on your current installation, the upgrade procedure will differ.
If you are running Postgres Pro Standard version 18.104.22.168 or higher, it is enough to install the 22.214.171.124 version into the same directory. However, if you are upgrading from PostgreSQL 9.5.x or lower versions of Postgres Pro Standard, some catalog changes should be applied, so pgpro_upgrade script is required to complete the upgrade:
If you are upgrading your installation from a binary package, and your database is in the default location,
pgpro_upgradeis run automatically, unless you are prompted to run it manually.
If you compiled Postgres Pro from source code or created your database in a non-default location, you must run
pgpro_upgrade manually, you must stop the
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.
To migrate to this version from vanilla PostgreSQL 9.5.4 or lower, perform a dump/restore using pg_dumpall.