<sect1 id="release-pro-9-6-5-1">

<title>Postgres Pro 9.6.5.1</title>

<note>

<title>Release Date</title>

<simpara>2017-08-30</simpara>

</note>

<sect2>

<title>Overview</title>

<para>This release is based on <productname>Postgres Pro</productname>

<link linkend="release-pro-9-6-4-1">9.6.4.1</link> and

<productname>PostgreSQL</productname> <link linkend="release-9-6-5">9.6.5</link>.</para>

<para>Major enhancements over <productname>Postgres Pro</productname>

9.6.4.1 include:</para>

<itemizedlist>

<listitem>

<para>Updated <application>pg_pathman</application> module to

version 1.4.3. (See <xref linkend="pg-pathman"> and <xref linkend="pg-pathman-how-to-update">.)

As compared to version 1.4.2, the following enhancements were introduced:</para>

<itemizedlist spacing="compact">

<listitem>

<para>Disabled dangerous optimizations for <command>UPDATE</command> and <command>DELETE</command> on <productname>PostgreSQL</productname> 9.5.

</para>

</listitem>

<listitem>

<para>Fixed the following type of query: <command>DELETE FROM single_table USING partitioned_table</command>.

</para>

</listitem>

<listitem>

<para>Fixed the output of the <command>EXPLAIN INSERT INTO partitioned_table</command> command when verbose mode is activated.

</para>

</listitem>

</itemizedlist>

<para>For a full list of changes,

see <ulink url="https://github.com/postgrespro/pg_pathman/releases/"><application>pg_pathman</application> Wiki</ulink>.

</para>

</listitem>

<listitem>

<para>Enhanced the <xref linkend="app-pgcontroldata"> utility

to enable automatic <productname>Postgres Pro</productname> upgrades

using the <literal>pgpro_upgrade</literal> script.

</para>

</listitem>

</itemizedlist>

</sect2>

<sect2>

<title>Migration to Version 9.6.5.1</title>

<para>Depending on your current installation, the upgrade procedure will differ.

</para>

<para>To upgrade from a <productname>Postgres Pro</productname> version based on

any previous <productname>PostgreSQL</productname> major release, you can perform a dump/restore using

<xref linkend="app-pg-dumpall">, or use the <xref linkend="pgupgrade"> utility.

The first option is safer, while the second is faster and can

speed up the upgrade process for large databases.

</para>

<para>To upgrade from a <productname>Postgres Pro</productname> version

based on the same <productname>PostgreSQL</productname> major release,

the <literal>pgpro_upgrade</literal> script provided

in this distribution is required:

<itemizedlist>

<listitem>

<para>If you are upgrading your <productname>Postgres Pro</productname>

installation from a binary package, the <literal>pgpro_upgrade</literal> script

is run automatically, or you are prompted to run it manually.

</para>

</listitem>

<listitem>

<para>If you have compiled <productname>Postgres Pro</productname>

from source code or created your database in a non-default location,

you must always run the <literal>pgpro_upgrade</literal> script manually.

Before running the script, you should stop postgres service.

Script should be run on behalf of the user owning the database

(typically postgres) and PGDATA environment variable should be

set to the directory where database resides.

</para>

</listitem>

</itemizedlist>

<note>

<para>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

<filename>pgsql</filename> to the <filename>pgpro</filename>

directory before running the <literal>pgpro_upgrade</literal> script.

Besides, after you upgrade to a newer version, you will have to use

the <literal>systemd</literal> service manager.

</para>

</note>

</para>

<para>To migrate from vanilla PostgreSQL 9.6.x, perform a dump/restore using

<xref linkend="app-pg-dumpall">.

</para>

</sect2>

</sect1>