Updated RN 9.6.8.2

Author: dmpgpro

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

@@ -1,5 +1,106 @@
 <!-- doc/src/sgml/release-pro-9.6.sgml -->
 <!-- See header comment in release.sgml about typical markup -->
+<sect1 id="release-pro-9-6-8-2">
+  <title>Postgres Pro Standard 9.6.8.2</title>
+  <formalpara>
+    <title>Release date:</title>
+    <para>2018-03-20</para>
+  </formalpara>
+  <sect2>
+    <title>Overview</title>
+    <para>This release is based on <productname>PostgreSQL</productname> 9.6.8
+      and <productname>Postgres Pro Standard</productname> 9.6.8.1. All improvements
+      inherited from <productname>PostgreSQL</productname> 9.6.8 are listed
+      in <link linkend="release-9-6-8"><productname>PostgreSQL</productname> 9.6.8 Release Notes</link>.</para>
+    <para>Major enhancements over <productname>Postgres Pro Standard</productname>
+      9.6.8.1 include:</para>
+    <itemizedlist>
+      
+      <listitem>
+        <para>Updated
+          the <link linkend="app-pgprobackup"><application>pg_probackup</application></link>
+          utility from version 2.0.11 to 2.0.16, which includes the following new features:</para>
+        <itemizedlist>
+          <listitem>    
+            <para>Infinite loop while page validation has been fixed.</para>
+          </listitem>
+          <listitem>
+            <para>Fixed segfault for the case of parallel ptrack connections.</para>
+          </listitem>
+          <listitem>
+            <para>Allowed to use delete-wal option wihtout delete-expired.</para>
+          </listitem>
+          <listitem>
+            <para>Allowed to use pg_ptrack_get_block if it is available and page is invalid.</para>
+          </listitem>
+          <listitem>
+            <para>Fixed CVE-2018-1058. Schema name explicitly used on the every function call.</para>
+           </listitem>
+        </itemizedlist>
+        <!-- 
+           76afcee1255d94ebc84f89ba336827999436a4c2
+        -->        
+      </listitem>
+      <listitem>
+        <para>
+          Reverted incorrect replacement of <function>pgpro_build</function>
+          with <function>pgpro_source_id</function> function.
+        </para>
+        <!--
+            f26daaf0d3257d4bc8ed8b59d7e560d37a61117e
+          -->
+      </listitem>      
+    </itemizedlist>
+  </sect2>
+  <sect2>
+    <title>Migration to Version 9.6.8.2</title>
+    <para>Depending on your current installation, the upgrade procedure will differ.
+    </para>
+    <para>To upgrade from a <productname>Postgres Pro Standard</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 Standard</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 Standard</productname> 9.6.7.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 Standard</productname> 9.6.4.1, as well as
+      rename the <function>pgpro_build</function> function to <function>pgpro_source_id</function>.
+      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-8-1">
   <title>Postgres Pro Standard 9.6.8.1</title>
   <formalpara>