DOC: reviewed RNs for PGPRO 10.3.2

Author: Liudmila Mantrova

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

@@ -9,10 +9,9 @@
   <sect2>
     <title>Overview</title>
     <para>This release is based on <productname>PostgreSQL</productname> 10.3
-    and includes all the new features introduced in PostgreSQL 10, as well as
-    bug fixes implemented in PostgreSQL 10.3. For their detailed description,
-    see <link linkend="release-10">PostgreSQL 10 Release Notes</link> and
-    <link linkend="release-10-3">PostgreSQL 10.3 Release Notes</link>, respectively.
+    and <productname>Postgres Pro Standard</productname> 10.3.1. All
+    changes inherited from <productname>PostgreSQL</productname> 10.3 are listed in
+    <link linkend="release-10-3"><productname>PostgreSQL</productname> 10.3 Release Notes</link>.
     Other major changes and enhancements are as follows:</para>
     <itemizedlist spacing="compact">
       <listitem>
@@ -23,53 +22,65 @@
       </listitem>
       <listitem>
         <para>
-          Fixed search for mchar and mvarchar types via search_path to make
-          these types dumpable even with cleaned up search path.
+          Fixed search for <type>mchar</type> and <type>mvarchar</type> types via
+          <varname>search_path</varname>. These types can now be dumped even with
+          the cleaned up search path.
         </para>
         <!-- 355211667eaf7469696b3316ef7b935c6cc9e78c -->
       </listitem>
       <listitem>
         <para>
-          Added <literal>--add-collprovider</literal> option to <command>pg_dump</command> utility.
+          Added <literal>--add-collprovider</literal> option to
+          <command>pg_dump</command> and <command>pg_dumpall</command> utilities.
         </para>
         <!-- 431100a1cd03808b0dc1cdfdd065398ec08b59e1 -->
       </listitem>
       <listitem>
         <para>Updated the <link linkend="app-pgprobackup"><application>pg_probackup</application></link>
-          utility from 2.0.14 to 2.0.16 version.</para>
+          utility from version 2.0.14 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 <literal>delete-wal</literal> option wihtout <literal>delete-expired</literal>.</para>
-            </listitem>
-            <listitem>
-              <para>Allowed to use <literal>pg_ptrack_get_block</literal> 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>
-            <listitem>
-              <para>Handle datafiles in directory <literal>global</literal> as datafiles.</para>
-            </listitem>
-            <listitem>
-              <para>Do not copy ptrack files from directory <literal>global</literal> to backup anymore.</para>
-            </listitem>
-            <listitem>
-              <para>
-                Check if <literal>--instance</literal> is specified for <command>VALIDATE</command> with target parameters.
-              </para>
-            </listitem>            
-          </itemizedlist>
+            <para>Fixed an infinite loop that could happen during page validation.</para>
+          </listitem>
+          <listitem>
+            <para>Fixed segfault for the case of parallel <literal>PTRACK</literal> connections.</para>
+          </listitem>
+          <listitem>
+            <para>Allowed to use the <literal>delete-wal</literal> option without <literal>delete-expired</literal>.</para>
+          </listitem>
+          <listitem>
+            <para>
+             Schema name is now explicitly used in all function calls
+             to address CVE-2018-1058 security issue.
+            </para>
+          </listitem>
+          <listitem>
+            <para>
+             Data files in the <filename>global</filename> directory
+             are now handled properly: <application>pg_probackup</application>
+             can now perform incremental backups and run checksum validation
+             for such data files.
+            </para>
+          </listitem>
+          <listitem>
+            <para>
+             <literal>PTRACK</literal> files from the <filename>global</filename>
+             directory are not copied to backups anymore.
+            </para>
+          </listitem>
+          <listitem>
+            <para>
+             <application>pg_probackup</application> now checks that the
+             <literal>--instance</literal> option is specified for the
+             <literal>VALIDATE</literal> command.
+            </para>
+          </listitem>
+        </itemizedlist>
         <!-- 76afcee1255d94ebc84f89ba336827999436a4c2 -->
       </listitem>
       <listitem>
-        <para>Fixed problem with sort order of some russian letters in the
-          mchar module.
+        <para>Fixed an issue with sort ordering of some Russian letters in the
+          <filename>mchar</filename> module.
           Use <command>REINDEX DATABASE</command> command to update indexes.</para>
         <!-- 06113a6d9d0fc9b88346c69011158b589ca487e7 -->
       </listitem>
@@ -85,7 +96,9 @@
     <para>To migrate from <productname>PostgreSQL</productname> or
       <productname>Postgres Pro Standard</productname> versions based on
       any previous <productname>PostgreSQL</productname> major release, see the instructions
-      in <link linkend="release-pro-10-3-1">Postgres Pro Standard 10.3.1 Release Notes</link>.
+      in <link linkend="release-pro-10-1-1">Postgres Pro Standard 10.1.1 Release Notes</link>.
+      If you are opting for a dump/restore, make sure to use the <literal>--add-collprovider</literal>
+      option to correctly choose the collation provider for the migrated database.
     </para>
 
   </sect2>