<!-- doc/src/sgml/release-pro-9.5.sgml -->

<!-- See header comment in release.sgml about typical markup -->

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

<title>Postgres Pro 9.5.2.3</title>

<note>

<title>Release Date</title>

<simpara>2016-04-01</simpara>

</note>

<sect2>

<title>Overview</title>

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

9.5.2.

</para>

<para>

Note that PostgresPro doesn't suffer from abbreviated keys problem,

mentioned in the changes of upstream 9.5.2 release. When build with

<literal>--with-icu</literal> option, PostgresPro doesn't use

string comparation functions from system C library, and uses portable

implementations from <productname>libicu</productname>.

</para>

<para>Major enhancement in the <productname>Postgres Pro</productname>

9.5.2.3 over <productname>Postgres Pro</productname> 9.5.1.2 include:

</para>

<itemizedlist>

<listitem><para>Include pg_pathman module which provides functions for

declarative partitioning and optimizes query execution plans for

partitioned tables.</para>

</listitem>

<listitem><para>Include pg_arman incremental backup utlity. It is considered

an experimantal feature, so it is build as separate package on Linux

and is not available for Windows yet. Documentation is also provided

separately</para>

</listitem>

<listitem><para>

<literal>version()</> SQL function now returns <literal>PostgreSQL

9.5.2</literal>, as in vanilla PostgreSQL, because some client frameworks

such as <productname>SQL Alchemy</productname> are confused seeing

PostgresPro here. Function <literal>pgpro_version</literal> is provided

to report PostgresPro release.

</para>

</listitem>

</itemizedlist>

</sect2>

</sect1>

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

<title>Postgres Pro 9.5.1.1</title>

<title>Postgres Pro 9.5.1.2</title>

<note>

<title>Release Date</title>

<simpara>2016-02-26</simpara>

<simpara>Current as of 2016-02-19</simpara>

<simpara>2016-03-02</simpara>

</note>

<sect2>

<title>Overview</title>