Added RN 9.6.8.2 Ent

Author: dmpgpro

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

@@ -1,4 +1,76 @@
 <!-- doc/src/sgml/release-proee-9.6.sgml -->
+<sect1 id="release-proee-9-6-8-2">
+<title>&productname; 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>Postgres Pro Standard</productname> 9.6.8.2
+      and <productname>Postgres Pro Enterprise</productname> 9.6.8.1. All improvements
+      inherited from <productname>Postgres Pro Standard</productname> 9.6.8.2 are listed
+      in <link linkend="release-pro-9-6-8-2"><productname>Postgres Pro Standard</productname> 9.6.8.2 Release Notes</link>.</para>
+    <para>Main changes over <productname>Postgres Pro Enterprise</productname>
+      9.6.8.1 include:</para>
+    <itemizedlist>
+      <listitem>
+        <para>
+          Fixed and re-enabled the <application>pg_wait_sampling</application> module on
+          Windows systems.
+        </para>
+        <!--
+             e743a2bd729b97014d1eb7b0b701bd5ca5eab09f
+             bd4e5dd5c8ed5329ee5105f7e36afe59501ae2d6
+             49061bf5d5e8140b12db8f8c70d17dd8eb3847bf
+          -->
+      </listitem>
+    </itemizedlist>
+  </sect2>
+  <sect2>
+    <title>Migration to Version &productname; 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 Enterprise</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 Enterprise</productname> version
+      based on the same <productname>PostgreSQL</productname> major release,
+      a dump/restore is not required. Instead of the <literal>pg_upgrade</literal>,
+      you must use the <literal>pgpro_upgrade</literal> script provided
+      in this distribution. This script updates metadata information to
+      handle catalog number format change introduced in 
+      <productname>Postgres Pro Enterprise</productname> 9.6.4.1, as well as
+      renames the <function>pgpro_build</function> function to <function>pgpro_source_id</function>. If you are upgrading your
+      <productname>Postgres Pro Enterprise</productname> installation from a binary package, the
+      <literal>pgpro_upgrade</literal> script is run automatically, or 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) and PGDATA environment variable should be
+      set to the directory where database resides. Running <literal>pgpro_upgrade</literal>
+      as root will result in an error.
+        </para>
+      </important>
+      <note>
+        <para>On RPM-based Linux distributions, if you are upgrading from
+        version 9.6.1.2, make sure to move the data directory from
+        <filename>pgsql</filename> to the <filename>pgproee</filename>
+        directory before running the <literal>pgpro_upgrade</literal> script.
+        </para>
+      </note>
+    <para>To migrate from vanilla PostgreSQL 9.6.x or <productname>Postgres Pro</productname>,
+    perform a dump/restore using <xref linkend="app-pg-dumpall">.
+    </para>
+  </sect2>
+</sect1>
 <sect1 id="release-proee-9-6-8-1">
 <title>&productname; 9.6.8.1</title>
   <formalpara>