E.23. Postgres Pro Standard 9.6.6.1
Release date: 2017-11-14
E.23.1. Overview
This release is based on PostgreSQL 9.6.6 and Postgres Pro Standard 9.6.5.1. All improvements inherited from PostgreSQL 9.6.6 are listed in PostgreSQL 9.6.6 Release Notes.
Major enhancements over Postgres Pro Standard 9.6.5.1 include:
Updated pg_pathman module to version 1.4.8. (See pg_pathman and Section F.36.1.1.) As compared to version 1.4.3, the following enhancements were introduced:
Improved cache invalidation mechanisms.
Disabled
COPY
command. Usepartitioned_table
TOCOPY (SELECT * FROM
instead.partitioned_table
) TOFixed
INSTEAD OF
triggers on views selected from partitioned tables.ALTER TABLE
now also renames auto naming sequences.partitioned_table
RENAME TODisabled some dangerous optimizations for
SELECT ... FOR SHARE/UPDATE
on PostgreSQL 9.5.Improved error handling in concurrent partitioning background worker.
Prohibited execution of queries
DELETE FROM
andpartitioned_table_1
USINGpartitioned_table_2
...UPDATE
if such queries touch more than one partition ofpartitioned_table_1
FROMpartitioned_table_2
...partitioned_table_1
.Fixed a bug causing crashes on
RESET ALL
.Fixed
WHERE
conditions that point to gaps between partitions.Restored compatibility with pg_repack.
For the full list of changes, see pg_pathman Wiki.
Updated the pg_probackup utility from version 2.0.2 to 2.0.11, which includes the following new features:
Password prompt interruption is now handled correctly.
The provided passwords are checked to be is non-empty.
The files that have not changed since the previous backup are not included into the next incremental backup.
Database version is now added into backup meta information.
Other miscellaneous bug fixes.
E.23.2. Migration to Version 9.6.6.1
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. If you are upgrading from Postgres Pro Standard 9.6.5.1, it is enough to install the new version into your current installation directory. When upgrading from Postgres Pro Standard 9.6.4.1 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 9.6.4.1. If you are upgrading your Postgres Pro installation from a binary package, the pgpro_upgrade
script is run automatically, unless you are prompted to run it manually.
Important
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.
If you have compiled Postgres Pro from source code or created your database in a non-default location, you must run the pgpro_upgrade
script manually.
Note
On RPM-based Linux distributions, if you are upgrading from version 9.6.2.1 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, perform a dump/restore using pg_dumpall.