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

<title>Postgres Pro 9.6.2.1</title>

<note>

<title>Release Date</title>

<simpara>2017-02-__</simpara>

</note>

<sect2>

<title>Overview</title>

<para>This release is based on <productname>PostgresPro</productname>

9.6.1.2 and <productname>PostgreSQL</productname> 9.6.2.</para>

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

9.6.1.2 include:</para>

<itemizedlist>

<listitem>

<para>Module <application>pg_pathman</application> has been updated to version 1.3 (See <xref linkend="pg-pathman">).</para>

</listitem>

<listitem>

<para>The <application>sr_plan</application> module is now initialized independently for each database instance (See <xref linkend="sr-plan">).</para>

</listitem>

<listitem>

<para>Applied fixes for including indexes.</para>

</listitem>

<listitem>

<para>RHEL-based distributions are installed in a separate location,

so the product can be installed in parallel with an existing

<productname>PostgreSQL</productname>.</para>

</listitem>

<listitem>

<para>Improved the algorithm of automatic TCP-port selection for the case

of parallel installation of different versions of the product on

Windows systems.</para>

</listitem>

</itemizedlist>

</sect2>

<sect2>

<title>Migration to Version 9.6.2.1</title>

<para>A dump/restore using <xref linkend="app-pg-dumpall">, or

use of <xref linkend="pgupgrade">, is required for those

wishing to migrate data from any previous major release.

</para>

<para>A dump/restore is not required for those running 9.6.1.2.</para>

<para>However, if you are upgrading from vanilla PostgreSQL 9.6.x, some

catalog changes should be applied.

</para>

<para>If you use binary packages, and your database is in the default

location, this upgrade should be performed automatically. If you've

compiled Postgres Pro from source or create your database in a

non-default location, running <literal>initdb</literal> manually, you

should run <literal>pgpro_upgrade</literal> script provided in this

distribution.

</para>

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

</sect2>

</sect1>