Added RN 10.4.1

Author: dmpgpro

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

@@ -1,5 +1,96 @@
 <!-- doc/src/sgml/release-pro-10.sgml -->
 <!-- See header comment in release.sgml about typical markup -->
+<sect1 id="release-pro-10-4-1">
+  <title>Postgres Pro Standard 10.4.1</title>
+  <formalpara>
+    <title>Release Date:</title>
+    <para>2018-05-15</para>
+  </formalpara>
+  <sect2>
+    <title>Overview</title>
+    <para>This release is based on <productname>PostgreSQL</productname> 10.4
+    and <productname>Postgres Pro Standard</productname> 10.3.2. All
+    changes inherited from <productname>PostgreSQL</productname> 10.4 are listed in
+    <link linkend="release-10-4"><productname>PostgreSQL</productname> 10.4 Release Notes</link>.
+    Other major changes and enhancements are as follows:</para>
+    <itemizedlist spacing="compact">
+      <listitem>
+        <para>
+          Fixed problem with sort order of some russian letters in
+          the <literal>mchar</literal> module. (See: <xref linkend="release-pro-10-4-1-migration">)</para>
+        <!-- 0b2c2188726e50454385b842aa7d5cdaf52d088e -->
+      </listitem>
+      <listitem>
+        <para>Updated <filename>pg_pathman</filename> module to
+          version 1.4.11. As compared to version 1.4.9, the following enhancements were introduced:
+          <itemizedlist>
+            <listitem>
+              <para>
+                Fixed an issue with duplicate entries in query results for inherited tables.
+                In general, <filename>pg_pathman</filename> does not support multilevel partitioning.     
+              </para>
+            </listitem>
+            <listitem>
+              <para>
+                Fixed a spurious <literal>table is being partitioned now</literal> error raised
+                by <function>partition_table_concurrently()</function>.
+              </para>
+            </listitem>
+            <listitem>
+              <para>
+                Relaxed check constraint handling.
+              </para>
+            </listitem>
+            <listitem>
+              <para>
+                Fixed incorrect usage of <function>memcpy()</function> in <function>start_bgworker()</function>.
+              </para>
+            </listitem>
+            <listitem>
+              <para>For a full list of changes,
+                see <ulink url="https://github.com/postgrespro/pg_pathman/releases/"><application>pg_pathman</application> Wiki</ulink>.
+              </para>
+            </listitem>
+          </itemizedlist>
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Added <literal>pgpro-version</literal> and <literal>pgpro-edition</literal> options to <command>pg_config</command>.
+        </para>
+        <!-- dd56e2dd71ac743bff78c53aca56cb5ed0f68843 -->
+      </listitem>
+      <listitem>
+        <para>
+          Reloading of the <literal>recovery.conf</literal> on recieving <command>SIGHUP</command> signal.
+        </para>
+        <!-- b311922c412d5193a47b63fe8fe0e70c7e82dc93 -->
+      </listitem>
+    </itemizedlist>
+  </sect2>
+  <sect2 id="release-pro-10-4-1-migration">
+    <title>Migration to Version 10.4.1</title>
+
+    <para>If you are upgrading from a <productname>Postgres Pro Standard</productname> version
+      based on the same <productname>PostgreSQL</productname> major release,
+      it is enough to install the new version into your current installation directory.
+    </para>
+    <para>
+      After upgrade from version <productname>Postgres Pro Standard</productname>
+      10.3.2 or lesser you must be call <command>REINDEX</command> command
+      for indexes which used <literal>mchar</literal> or
+      <literal>mvarchar</literal> types.
+    </para>
+    <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-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>
+</sect1>
 <sect1 id="release-pro-10-3-2">
   <title>Postgres Pro Standard 10.3.2</title>
   <formalpara>