E.19. Postgres Pro Standard 9.6.9.1
Release date: 2018-05-23
E.19.1. Overview
This release is based onPostgreSQL 9.6.9 andPostgres Pro Standard 9.6.8.2. All improvements inherited fromPostgreSQL 9.6.9 are listed inPostgreSQL 9.6.9 Release Notes.
Major enhancements overPostgres Pro Standard 9.6.8.2 include:
Updated theSection F.29 to fix the sorting order for Cyrillic letters Yo and short I. Make sure to run the
REINDEXcommand to rebuild indexes that usemcharormvarchartypes.Updated thepg_probackup utility to version 2.0.17, which includes the following new features:
DELTAmode for incremental backups that reads all data files in the data directory and creates an incremental backup for pages that have changed since the previous backup.New options for
restoreandvalidatecommands:--immediateoption ends recovery as soon as a consistent state is reached.--recovery-target-actionoption specifies the action the server should take when the recovery target is reached.--recovery-target-namespecifies a named savepoint up to which to restore the cluster data.--write-recovery-confwrites a minimalrecovery.confin the output directory to facilitate setting up a standby server.
For details, seepg_probackup.
Updated PTRACK to version 1.6:
Now ptrack doesn't track unlogged relations.
Updatedjsquery module.
Updated
pg_pathmanmodule to version 1.4.11. As compared to version 1.4.9, the following enhancements were introduced:Fixed an issue with duplicate entries in query results for inherited tables. In general,
pg_pathmandoes not support multilevel partitioning.Fixed a spurious
table is being partitioned nowerror raised bypartition_table_concurrently().Relaxed check constraint handling.
Fixed incorrect usage of
memcpy()instart_bgworker().For a full list of changes, seepg_pathman Wiki.
Performed multiple bug fixes in theshared_ispell module.
ImprovedPostgres Pro Standard version for Windows:
Fixed an issue with pasting strings that include symbols of different character sets from clipboard to psql on Windows systems.
Updated optimization algorithm for default database configuration.
You can now turn off configuration optimization when installingPostgres Pro from the command line by setting the
needoptimizationoption in the INI file to0.
E.19.2. Migration to Version 9.6.9.1
Depending on your current installation, the upgrade procedure will differ.
To upgrade from aPostgres Pro Standard version based on any previousPostgreSQL major release, make sure you have installed its latest minor version, and then perform a dump/restore usingpg_dumpall or use thepg_upgrade utility.
Important
When upgrading from versions 9.6.8.2 or lower, you must call theREINDEX command for indexes that usedmchar ormvarchar types.
To upgrade from aPostgres Pro Standard version based on the samePostgreSQL major release, a dump/restore is not required. If you are upgrading fromPostgres Pro Standard 9.6.7.1 or lower, you must also use thepgpro_upgrade script provided in this distribution. This script updates metadata information to handle catalog number format change introduced afterPostgres Pro Standard 9.6.4.1, as well as rename thepgpro_build function topgpro_source_id. If you are upgrading yourPostgres Pro installation from a binary package, thepgpro_upgrade script is run automatically, unless you are prompted to run it manually.
Important
If you runpgpro_upgrade manually, you must stop postgres service. The script must be run on behalf of the user owning the database (typically postgres). Runningpgpro_upgrade as root will result in an error. For details, seepgpro_upgrade.
If you have compiledPostgres Pro from source code or created your database in a non-default location, you must run thepgpro_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 frompgsql to thepgpro directory before running thepgpro_upgrade script.
To migrate from vanilla PostgreSQL 9.6.x, perform a dump/restore usingpg_dumpall.