DOC: added release notes for PGPROEE 10.3.3

Author: Liudmila Mantrova

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

@@ -1,4 +1,76 @@
 <!-- doc/src/sgml/release-proee-10.sgml -->
+<sect1 id="release-proee-10-3-3">
+<title>Postgres Pro Enterprise 10.3.3</title>
+  <formalpara>
+    <title>Release date:</title>
+    <para>2018-03-30</para>
+  </formalpara>
+  <sect2>
+    <title>Overview</title>
+    <para>This release is based on <productname>Postgres Pro Standard</productname> 10.3.2
+      and <productname>Postgres Pro Enterprise</productname> 10.3.2.
+      All changes inherited from <productname>Postgres Pro Standard</productname> 10.3.2
+      are listed in <link linkend="release-pro-10-3-2"><productname>Postgres Pro Standard</productname> 10.3.2 Release Notes</link>.
+      As compared with <productname>Postgres Pro Enterprise</productname> 10.3.2,
+      this version provides the following changes:</para>
+    <itemizedlist>
+      <listitem>
+        <para>
+          Fixed a bug in building B-tree indexes with optimized duplicate keys.
+          This issue does not affect unique indexes, primary keys,
+          catalog indexes, and covering indexes with the
+          <command>INCLUDE</command> clause. Other indexes have to be rebuilt.
+          <!-- cda4e22c3fde59c2b530310e608de315a2082c52
+          -->
+        </para>
+      </listitem>
+      <listitem>
+        <para>
+          Improved <application>multimaster</application> extension:
+        <itemizedlist>
+         <listitem>
+          <para>
+           <application>multimaster</application> now supports <command>UPDATE</command>
+           operations on tables without primary keys.
+           <!-- a2b65205637b9dc223f9bf1a376953f6c90d773a
+           -->
+          </para>
+         </listitem>
+         <listitem>
+          <para>
+           In cluster configurations with a <application>referee</application> node,
+           it is ensured that the voting result is discarded from the referee node
+           if all the cluster nodes can access each other. It allows to choose
+           a new winner in case of a failure.
+           See <xref linkend="setting-up-a-referee"> for details.
+           <!-- 7688caf4ece072af8e2f7fea10cf283c90f19e6e
+           -->
+          </para>
+         </listitem>
+        </itemizedlist>
+        </para>
+      </listitem>
+    </itemizedlist>
+  </sect2>
+  <sect2>
+    <title>Migration to Version 10.3.2</title>
+
+    <para>If you are upgrading from a <productname>Postgres Pro Enterprise</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>To migrate from <productname>PostgreSQL</productname>,
+      <productname>Postgres Pro Standard</productname>, or
+      <productname>Postgres Pro Enterprise</productname> versions based on
+      any previous <productname>PostgreSQL</productname> major release, see the instructions
+      in <link linkend="release-proee-10-1-1">Postgres Pro Enterprise 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-proee-10-3-2">
 <title>Postgres Pro Enterprise 10.3.2</title>
   <formalpara>