Update release notes from XL 10r1 GA release

diff --git a/doc/src/sgml/release-xl-10r1.sgml b/doc/src/sgml/release-xl-10r1.sgml
index 5da8f570b68c89a1dca592b866d865dfe9dd88a9..dced8f61c6d3e0d9c75fb63611ffcdc7071e53ea 100644 (file)
--- a/doc/src/sgml/release-xl-10r1.sgml
+++ b/doc/src/sgml/release-xl-10r1.sgml
@@ -1,12 +1,12 @@
 <!-- doc/src/sgml/release-xl-10r1.sgml -->
 <!-- See header comment in release.sgml about typical markup -->
- <sect1 id="release-xl-10r1beta1">
-  <title>Postgres-XL Release 10r1beta1</title>
+ <sect1 id="release-xl-10r1">
+  <title>Postgres-XL Release 10r1</title>
 
   <note>
    <title>Release Date</title>
-   <simpara>2018-09-17</simpara>
-   <simpara>Current as of 2018-09-17</simpara>
+   <simpara>2018-10-??</simpara>
+   <simpara>Current as of 2018-10-??</simpara>
   </note>
 
   <sect2>
@@ -22,7 +22,7 @@
 
    <para>
     PostgreSQL 9.6 added query parallelism and PostgreSQL 10 added declarative
-    partitioning. Both these features are now available in Postgres-XL 10r1beta1.
+    partitioning. Both these features are now available in Postgres-XL 10r1.
     Both these features come with certain limitations and hence users are advised
     to test these new features thoroughly before deploying applications.
    </para>
@@ -47,9 +47,9 @@
   </sect2>
 
   <sect2>
-  <title>Migration to Postgres-XL 10r1beta1 </title>
+  <title>Migration to Postgres-XL 10r1 </title>
    <sect3>
-   <title>Migration to Postgres-XL 10r1beta1 from PostgreSQL 10 </title>
+   <title>Migration to Postgres-XL 10r1 from PostgreSQL 10 </title>
     <para>
      A dump/restore using <xref linkend="app-pg-dumpall">
      is required for those wishing to migrate
@@ -61,10 +61,10 @@ linkend="pgupgrade">, as a mechanism to upgrade from PostgreSQL 10.
     </para>
    </sect3>
    <sect3>
-   <title>Migration to Postgres-XL 10r1beta1 from Postgres-XL 9.5r1.x </title>
+   <title>Migration to Postgres-XL 10r1 from Postgres-XL 9.5r1.x </title>
     <para>
-     Version 10r1beta1 contains a number of changes that may affect compatibility
-     with previous releases. Since Postgres-XL 10r1beta1 release includes all changes
+     Version 10r1 contains a number of changes that may affect compatibility
+     with previous releases. Since Postgres-XL 10r1 release includes all changes
 from PostgreSQL 9.6 and PostgreSQL 10 releases, it is
 recommended that you review respective release notes of those releases to find
 the exact incompatibilities.
@@ -73,9 +73,9 @@ the exact incompatibilities.
   </sect2>
 
   <sect2>
-   <title>Major Enhancements in Postgres-XL 10r1beta1 </title>
+   <title>Major Enhancements in Postgres-XL 10r1 </title>
    <para>
-    <productname>Postgres-XL</productname> 10r1beta1 is the first major release
+    <productname>Postgres-XL</productname> 10r1 is the first major release
 after <productname>Postgres-XL</productname> 9.5r1 release. So this release
 contains most of the major enhancements that went into
 <productname>PostgreSQL</productname> releases 9.6 and 10. This is a very
@@ -107,7 +107,7 @@ otherwise stated.
 
    <para>
     Below you will find a detailed account of the changes between
-    <productname>Postgres-XL</productname> 10r1beta1 and the previous major
+    <productname>Postgres-XL</productname> 10r1 and the previous major
     release.
    </para>
 
@@ -213,8 +213,35 @@ automatically compiled and installed along with other binaries.
   <itemizedlist> 
       <listitem>
        <para>
-        Make improvements to cluster monitor process and global state
-reporting.
+        Use binary-upgrade facilities to ensure consistent column ordering
+        while adding a new coordinator/datanode using
+        <application>pg_dump</application>/<application>pg_restore</application>.
+       </para>
+      </listitem>
+      <listitem>
+       <para>
+        Ensure GUC changes by user-defined functions are rolled back correctly. 
+       </para>
+       <para>
+        When a function body has SET clauses attached to it, the function
+        validation/execution reflects those GUC changes locally as well as on the
+        remote nodes. But we were failing to restore the old values back when the
+        function execution ends. That issue is now addressed.
+       </para>
+      </listitem>
+      <listitem>
+       <para>
+        Ensure CREATE TABLE (LIKE INCLUDING ALL) honors distribution strategy.
+       </para>
+      </listitem>
+      <listitem>
+       <para>
+        Fix a stack corruption by using dynamic buffer to parse NODE_LIST_RESULT in GTM.
+       </para>
+      </listitem>
+      <listitem>
+       <para>
+        Make improvements to cluster monitor process and global state reporting.
        </para>
       </listitem>
       <listitem>
@@ -352,7 +379,8 @@ funding and resources become available.
    </listitem>
    <listitem>
     <para>
-    User defined functions have several limitations.
+    User defined functions have several limitations, especially when executed
+on the datanodes, either directly or indirectly.
     </para>
    </listitem>
    <listitem>
@@ -425,8 +453,8 @@ distribution column values.
    </listitem>
    <listitem>
     <para>
-     All partitions of a partitioned table must have consistent column ordering
-and column positioning.
+     The distribution column position must be the same on all partitions of a
+partitioned table.
     </para>
    </listitem>
   </itemizedlist>