E.32. Postgres Pro Standard 9.6.0.1
Release date: 2016-10-12
E.32.1. Overview
This release is based onPostgreSQL9.6.0.
Major enhancements overPostgreSQL 9.6.0 include:
Core patches fromPostgres Pro 9.5 has been applied:
Covering indices patch by Anastasia Lubennikova (Commit: 91b4e25614247833d7960c49d783f69b90c0c149) (Details:http://www.postgresql.org/message-id/f90aa60a-b67f-95b5-d9f5-f5d8ced178c6@postgrespro.ru/
ICU patch (Commit: ee711324f31cc039e656ea45c54abd0cf8ea3e41)
Fixes to win32 build system (Commit: 84fa653ee00ebe54f591b18e3664fa6d5889224f)
Added pgpro_version SQL function and appropriate defines into pg_config.h (Commit: 671a7525541aa3eece366dae4249aa43a56a2168)
Integrated PTRACK patch (Commit: cea0987364070600fe640df0050d285b53cafb00)
Added order by to index_including test to make 32-bit FreeBSD happy (Commit: fd9fc27d40b5dd4db611418bb848760154ec9f55)
Modules has been ported fromPostgres Pro 9.5
hunspell-dict (SeeHunspell Dictionaries Modules)
jsquery (SeeSection F.26)
pg_variables (SeeSection F.44)
pg_pathman (Seepg_pathman)
pg_query_state (SeeSection F.38)
shared-ispell (Seeshared_ispell)
sr_plan (Seesr_plan)
dump_stat (Seedump_stat)
Tools has been ported fromPostgres Pro 9.5
pg_arman
E.32.2. Migration to Version 9.6.0.1
A dump/restore usingpg_dumpall, or use ofpg_upgrade, is required for those wishing to migrate data from any previous release.
Dump/restore is not necessary when migrating from PostgreSQL 9.6.x toPostgres Pro Standard 9.6.x.y.
When upgrading from previous releases ofPostgres Pro or from vanilla PostgreSQL 9.6.x, some catalog changes should be applied.
If you use binary packages, and your database is in the default location, this upgrade should be performed automatically. If you've compiledPostgres Pro from source or create your database in non-default location, runninginitdb manually, you should runpgpro_upgrade script provided in this distribution.
Before running script, you should stop postgres service. Script should be run as user, owning the database (typically postgres) and PGDATA environment variable should be set to the directory where database resides.