Added RN 9.6.7.1

Author: dmpgpro

doc/src/sgml/release-pro-9.6.sgml

@@ -1,5 +1,112 @@
 <!-- doc/src/sgml/release-pro-9.6.sgml -->
 <!-- See header comment in release.sgml about typical markup -->
+<sect1 id="release-pro-9-6-7-1">
+  <title>Postgres Pro 9.6.7.1</title>
+  <formalpara>
+    <title>Release date:</title>
+    <para>2018-02-14</para>
+  </formalpara>
+  <sect2>
+    <title>Overview</title>
+    <para>This release is based on <productname>PostgreSQL</productname> 9.6.7
+      and <productname>Postgres Pro</productname> 9.6.6.1. All improvements
+      inherited from <productname>PostgreSQL</productname> 9.6.7 are listed
+      in <link linkend="release-9-6-7"><productname>PostgreSQL</productname> 9.6.7 Release Notes</link>.</para>
+    <para>Major enhancements over <productname>Postgres Pro</productname>
+      9.6.6.1 include:</para>
+    <itemizedlist>
+      <listitem>
+        <para>Updated <xref linkend="pg-pathman"> module to
+          version 1.4.9. This version fixes handling of <literal>ONLY</>
+          in all kinds of queries.
+          (See <xref linkend="pg-pathman"> and <xref linkend="pg-pathman-how-to-update">.)
+        </para>
+        <!--
+            675ce6923c065cf213acf58a060ed0c82656d80a
+          -->
+      </listitem>
+      <listitem>
+        <para>Updated <application>dump_stat</application> module to
+          version 1.1 that provides several bug fixes.
+          (See <xref linkend="dump-stat">.)</para>
+        <!--
+            708f5b7d8d045e1998819fe2524fa77201162411
+          -->
+      </listitem>
+      <listitem>
+        <para>Updated the PTRACK patch to version 1.4.</para>
+        <!--
+            35ff8555d9267b623c4a821f876280a6e1dd0904
+            bee82cd96affc07e59a755d4338239684135d5e3
+          -->
+      </listitem>
+      <listitem>
+        <para>Dynamic prepare of the <command>psql</command> history path on the Windows systems.</para>
+        <!--
+            f55eb174f44f39e27e8e1be3f40fe1a64993afc1
+            3a962d4a7e7dda33699a6475a9816adb88ae4d56
+          -->
+      </listitem>
+      <listitem>
+        <para>
+          In the B-tree indexes added support of TOAST to INCLUDED attributes.</para>
+        <!--
+            6ba76ea29415b5a78b92699919d5dcec0b618f03
+            02213a155d006f528b8594471bc436492d1a53c9
+            48644d698f5757365e294efd0482a4648234a655
+          -->
+      </listitem>
+    </itemizedlist>
+  </sect2>
+  <sect2>
+    <title>Migration to Version 9.6.7.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 significantly
+      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,
+      a dump/restore is not required. If you are upgrading from
+      <productname>Postgres Pro</productname> 9.6.6.1, it is enough to install the new
+      version into your current installation directory.
+      When upgrading from  <productname>Postgres Pro</productname> 9.6.4.1 or
+      lower, you must also use the <xref linkend="pgproupgrade"> script provided
+      in this distribution. This script updates metadata information to
+      handle catalog number format change introduced after 
+      <productname>Postgres Pro</productname> 9.6.4.1. If you are upgrading your
+      <productname>Postgres Pro</productname> installation from a binary package, the
+      <filename>pgpro_upgrade</filename> script is run automatically, unless you
+      are prompted to run it manually.
+      </para>
+      <important>
+        <para>
+      If you run <literal>pgpro_upgrade</literal> manually,
+      you must stop postgres service.
+      The script must be run on behalf of the user owning the database
+      (typically postgres). Running <literal>pgpro_upgrade</literal>
+      as root will result in an error. For details, see <xref linkend="pgproupgrade">.
+        </para>
+      </important>
+      <para>If you have compiled <productname>Postgres Pro</productname>
+      from source code or created your database in a non-default location,
+      you must run the <literal>pgpro_upgrade</literal> script manually.
+      </para>
+      <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.
+        </para>
+      </note>
+    <para>To migrate from vanilla PostgreSQL 9.6.x, perform a dump/restore using
+      <xref linkend="app-pg-dumpall">.
+    </para>
+  </sect2>
+</sect1>
 <sect1 id="release-pro-9-6-6-1">
   <title>Postgres Pro 9.6.6.1</title>
   <formalpara>