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

<title>Postgres Pro 9.6.3.2</title>

<note>

<title>Release Date</title>

<simpara>2017-07-12</simpara>

</note>

<sect2>

<title>Overview</title>

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

<link linkend="release-pro-9-6-3-1">9.6.3.1</link> and

<productname>PostgreSQL</productname> <link linkend="release-9-6-3">9.6.3</link>.</para>

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

9.6.3.1 include:</para>

<itemizedlist>

<listitem>

<para>Updated the <link linkend="app-pgprobackup"><application>pg_probackup</application></link> backup manager to version 2.0 that includes the following new features:</para>

<itemizedlist>

<listitem>

<para>

Saving backups for different databases in a single backup catalog

</para>

<para>

Storing backup data in a compressed state to save disk space

</para>

<para>

Extended logging settings

</para>

</listitem>

</itemizedlist>

</listitem>

<listitem>

<para>Added distribution for Debian 9.</para>

</listitem>

<listitem>

<para>Added upstream patches that fix potential data corruption during freeze.</para>

</listitem>

</itemizedlist>

</sect2>

<sect2>

<title>Migration to Version 9.6.3.2</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.3.1.</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>