DOC: style changes in Release notes for PGPRO10, added collation-related details for dump/restore

Author: Liudmila Mantrova

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

@@ -24,7 +24,8 @@
           -->
       </listitem>
       <listitem>
-        <para>Implemented dynamic prepare of the <command>psql</command> history path on Windows systems.</para>
+        <para>Implemented dynamic prepare of the default directory for storing
+          <command>psql</command> history on Windows systems.</para>
         <!--
              e80337e33aa37839e1a141f6d196096e1148cf17
              5850209dbff28912d1da44bcfab23f0e16907667
@@ -33,6 +34,24 @@
       <listitem>
         <para>Updated the <link linkend="app-pgprobackup"><application>pg_probackup</application></link>
           utility to version 2.0.14.</para>
+          <itemizedlist>
+            <listitem>
+              <para>
+               Fixed race conditions in <literal>ptrack</literal> and page backups.
+              </para>
+            </listitem>
+            <listitem>
+              <para>
+               Fixed parallel <literal>ptrack</literal> backup interruption.
+              </para>
+            </listitem>
+            <listitem>
+              <para>
+               Added new backup state <literal>ORPHAN</literal>, which indicates
+               that one of previous backups is corrupted.
+              </para>
+            </listitem>
+          </itemizedlist>
         <!-- fc40ff8949f10e50e0aaf805f69082539176626b -->
       </listitem>
       <listitem>
@@ -54,17 +73,16 @@
         <!-- efb70c83ccdead1e1d3604ec67eeae16c9fd26e5 -->
       </listitem>
       <listitem>
-        <para>Fixed incorrect handling of <literal>IS NULL / IS NOT NULL</literal>
-          quals in the indexes with included columns.</para>
+        <para>Fixed incorrect handling of <command>IS NULL</command> and <command>IS NOT NULL</command>
+          qual conditions in indexes with <command>INCLUDE</command> clauses.</para>
         <!-- 7bfe5275e91817dca49dd6e773130473e76c8183 -->
       </listitem>
       <listitem>
         <para>Added <literal>int2vector</literal> compatibility patch.</para>
         <!-- 0fc6e45196e78f479aa0fe95d5ff31aab6c67768 -->
       </listitem>
       <listitem>
-        <para>Module <application>online-analyze</application> has been
-          updated.</para>
+        <para>Updated <application>online-analyze</application> module.</para>
         <!-- adce42211d871c834d8ce339a241f866feb1a84b -->
       </listitem>
     </itemizedlist>
@@ -149,7 +167,21 @@
         you are recommended to use <literal>libc</literal> provider when
         upgrading from vanilla <productname>PostgreSQL</productname>, and
         omit the provider when upgrading from a previous version of
-        <productname>Postgres Pro</productname>.
+        <productname>Postgres Pro</productname>, unless you have databases with
+        non-C and non-POSIX collation settings. For such databases, you should
+        do the following:
+        <itemizedlist>
+          <listitem>
+            <para>If the new cluster is initialized with locales other than C or POSIX,
+            and the database has an single-byte encoding, set LC_COLLATE to '@libc' for this database.
+            </para>
+          </listitem>
+          <listitem>
+            <para>If the new cluster is initialized with C or POSIX locale settings and
+            the database has a multi-byte encoding, set LC_COLLATE to <literal>'@icu'</literal> for this database.
+            </para>
+          </listitem>
+        </itemizedlist>
       </para>
 
       <note>
@@ -401,7 +433,21 @@
         you are recommended to use <literal>libc</literal> provider when
         upgrading from vanilla <productname>PostgreSQL</productname>, and
         omit the provider when upgrading from a previous version of
-        <productname>Postgres Pro</productname>.
+        <productname>Postgres Pro</productname>, unless you have databases with
+        non-C and non-POSIX collation settings. For such databases, you should
+        do the following:
+        <itemizedlist>
+          <listitem>
+            <para>If the new cluster is initialized with locales other than C or POSIX,
+            and the database has an single-byte encoding, set LC_COLLATE to '@libc' for this database.
+            </para>
+          </listitem>
+          <listitem>
+            <para>If the new cluster is initialized with C or POSIX locale settings and
+            the database has a multi-byte encoding, set LC_COLLATE to <literal>'@icu'</literal> for this database.
+            </para>
+          </listitem>
+        </itemizedlist>
       </para>
 
       <note>