<!-- doc/src/sgml/release-proee-9.6.sgml -->

<sect1 id="release-proee-9-6-3-1">

<title>&productname; 9.6.3.1</title>

<note>

<title>Release Date</title>

<simpara>2017-05-25</simpara>

</note>

<sect2>

<title>Overview</title>

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

<link linkend="release-proee-9-6-2-1">9.6.2.1</link> and

<productname>Postgres Pro Standard</productname> <link linkend="release-pro-9-6-3-1">9.6.3.1</link>.</para>

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

9.6.2.1 include:</para>

<itemizedlist>

<listitem>

<para>Updated

the <link linkend="app-pgprobackup"><application>pg_probackup</application></link>

backup manager to version 1.1.11. Command-line interface

has been changed.</para>

</listitem>

<listitem><para>Improved <application>multimaster</application>

extension:

<itemizedlist>

<listitem>

<para>Added support for savepoints.

</para>

</listitem>

<listitem>

<para>Extended support for <acronym>DDL</acronym> statements.

</para>

</listitem>

</itemizedlist>

</para>

<para>(See <xref linkend="multimaster">.)</para>

</listitem>

<listitem><para>Enabled support for multiple data types in RUM index,

such as <literal>int</literal>, <literal>bigint</literal>,

<literal>float</literal>, <literal>time</literal>, <literal>interval</literal>,

<literal>bytea</literal>, <literal>text</literal>,

and more. You can now store <literal>tsvector</literal> type together

with other types in a single index.

</para><para>(See <xref linkend="rum">.)</para>

</listitem>

<listitem><para>Improved autonomous transaction support:

<itemizedlist>

<listitem>

<para>Fixed handling of multixact IDs.

</para>

</listitem>

<listitem>

<para>Speeded up execution of autonomous transactions.

</para>

</listitem>

</itemizedlist>

</para><para>(See <xref linkend="atx">.)</para>

</listitem>

</itemizedlist>

</sect2>

<sect2>

<title>Migration to Version &productname; 9.6.3.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>Dump/restore is necessary when migrating from <productname>PostgreSQL</productname>,

<productname>Postgres Pro Standard</productname>, or <productname>Postgres Pro Enterprise</productname> edition.</para>

<para>For upgrades from previous releases of <productname>Postgres Pro Enterprise</productname>, <productname>Postgres Pro Standard</productname>, or

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

created your database in

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

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

distribution.

</para>

<para>Before running the script, you should stop the <literal>postgres</literal> service.

The script should be run on behalf of the user owning the database

(typically <literal>postgres</literal>), and the <envar>PGDATA</envar> environment variable should be

set to the directory where the database resides.

</para>

</sect2>

</sect1>

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

<title>&productname; 9.6.2.1</title>

<note>

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

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

compiled <productname>Postgres Pro Enterprise</productname> from source orcreated your database in

created your database in

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

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

distribution.