Write release notes for upcoming Postgres-XL 9.5r1.2 release

diff --git a/doc/src/sgml/release-xl-9.5r1.sgml b/doc/src/sgml/release-xl-9.5r1.sgml
index 0cb85e65994b2ad25139b57050ce7c3b3ad7d64f..d020b94d1b87c2722928e76a461ea027c87ea647 100644 (file)
--- a/doc/src/sgml/release-xl-9.5r1.sgml
+++ b/doc/src/sgml/release-xl-9.5r1.sgml
@@ -1,6 +1,149 @@
 <!-- doc/src/sgml/release-9.5.sgml -->
 <!-- See header comment in release.sgml about typical markup -->
 
+ <sect1 id="release-xl-9-5r1.2">
+  <title>Postgres-XL Release 9.5r1.2</title>
+
+  <note>
+  <title>Release Date</title>
+  <simpara>2016-07-23</simpara>
+  </note>
+
+  <para>
+   This release contains a variety of fixes from Postgres-XL 9.5r1.1 release.
+   For information about new features in the Postgres-XL 9.5r1 major release, see
+   <xref linkend="release-xl-9-5r1">.
+  </para>
+  <sect2>
+   <title>Migration to Version Postgres-XL 9.5r1.1</title>
+   <para>
+    A dump/restore is not required for those running Postgres-XL 9.5r1 or
+Postgres-XL 9.5r1.1
+   </para>
+  </sect2>
+  <sect2>
+   <title>Changes</title>
+   <itemizedlist>
+    <listitem>
+     <para>
+      Fix a bug which would reset planner statistics of a table on the
+coordinator when an index is created on the table or when CLUSTER command is
+run on the table.
+     </para>
+    </listitem>
+    <listitem>
+     <para>
+      Make sure that the count of tuples affected by INSERT/DELETE/UPDATE is
+correctly computed when Fast-Query-Shipping is used.
+     </para>
+    </listitem>
+    <listitem>
+     <para>
+      Show remote node/backend and originating coordinator node/backend details
+in the ps output when a remote subplan is being executed on a datanode for each of debugging.
+     </para>
+    </listitem>
+    <listitem>
+     <para>
+      Ensure "init all" (and friends) does not remove existing data
+directories unless "force" option is specified by the caller.
+     </para>
+    </listitem>
+    <listitem>
+     <para>
+      Handle ON COMMIT actions on temporary tables appropriately on the datanodes.
+     </para>
+    </listitem>
+    <listitem>
+     <para>
+      Avoid pushing down evaluation of VALUES clause to a datanode for replicated
+tables, unless it contains volatile function(s).
+     </para>
+     <para>
+      This should provide a good performance boost for affected cases by
+avoiding another connection, thus reducing connection overhead as well as
+latency.
+     </para>
+    </listitem>
+    <listitem>
+     <para>
+      Fix a memory like while running ALTER TABLE DISTRIBUTE BY.
+     </para>
+    </listitem>
+    <listitem>
+     <para>
+      Use GTM_Sequence type to hold value of a sequence on GTM.
+     </para>
+     <para>
+      We were incorrectly using "int" at couple of places which is not wide
+enough to store 64-bit sequence values.
+     </para>
+    </listitem>
+    <listitem>
+     <para>
+      Never ever use an invalid XID, if we fail to connect to the GTM.
+     </para>
+     <para>
+      Earlier a node would happily proceed further if GTM becomes
+dead or unreachable. This may result in random problems since rest of the code
+is not prepared to deal with that situation (as seen from the crash in TAP
+tests).
+     </para>
+    </listitem>
+    <listitem>
+     <para>
+      Do not compute the relation size everytime rescanning a relation with
+    sequence scan.
+     </para>
+     <para>
+      This can provide big boost to performance when the inner side of a nested
+loop has a sequence scan with large number of rows in outer relation.
+     </para>
+    </listitem>
+    <listitem>
+     <para>
+      Block FOR SHARE/UPDATE for queries involving joins
+     </para>
+     <para>
+      Per report from Shaun Thomas, we don't yet support row locking when query
+has a join between tables. While it may sometimes give an error, worse it may
+silently lock wrong rows leading to application logic failures. The feature is
+now blocked until more appropriate fix is available.
+     </para>
+    </listitem>
+    <listitem>
+     <para>
+      Add several few regression test cases.
+     </para>
+    </listitem>
+    <listitem>
+     <para>
+      Use 2^32 modulo computation to convert signed integer to unsigned value
+since abs() may give a different result.
+     </para>
+     <para>
+      This makes the redistribution code in sync with the way hash modulo is
+computed elsewhere in the code. Earlier versions may have redistributed
+replicated tables wrongly when their distribution strategy is changed to hash
+or modulo distribution.
+     </para>
+    </listitem>
+    <listitem>
+     <para>
+      Load balance remote subplan execution by choosing a node randomly instead of
+always picking up the first node.
+     </para>
+     <para>
+      When planner has a choice of executing a subplan on any of the remote
+nodes, it always used to execute the subplan on the first node. That can cause
+excessive load/number of connections on that node. This change fixes that by
+choosing a node randomly from the list of available nodes.
+     </para>
+    </listitem>
+   </itemizedlist>
+  </sect2>
+ </sect1>
+
  <sect1 id="release-xl-9-5r1.1">
   <title>Postgres-XL Release 9.5r1.1</title>