svn commit - mysqldoc@docsrva: r8100 - trunk/refman-5.1

[jon]

Author: jstephens
Date: 2007-10-15 20:13:23 +0200 (Mon, 15 Oct 2007)
New Revision: 8100

Log:

Documented CGE-6.3.4 bugfixes:

  Bug #20435, Bug #25064, Bug #29390, Bug #29509, Bug #29656, 
  Bug #30379, Bug #30624, Bug #30975, Bug #30996, Bug #31097, 
  Bug #31257, Bug #31470, Bug #31525

Added release date to CGE-6.3.4 changelog.



Modified:
   trunk/refman-5.1/news-5.1.xml


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2007-10-15 17:24:16 UTC (rev 8099)
+++ trunk/refman-5.1/news-5.1.xml	2007-10-15 18:13:23 UTC (rev 8100)
Changed blocks: 3, Lines Added: 107, Lines Deleted: 5; 4833 bytes

@@ -813,7 +813,7 @@
 
     <section id="news-5-1-22-ndb-6-3-4">
 
-      <title>Changes in release MySQL 5.1.22-ndb-6.3.4-beta (Not yet
released)</title>
+      <title>Changes in release MySQL 5.1.22-ndb-6.3.4-beta (15 October
2007)</title>
 
       <para role="release-level">
         This is a new Beta development release, fixing recently

@@ -825,20 +825,17 @@
         [js] Uncomment next para following release.
       </remark>
 
-<!--
       <para>
         Like all releases for &mccge-series;, this is a source-only
         release which you must compile and install using the
         instructions found in <xref linkend="installing-source"/>, and
         in <xref linkend="mysql-cluster-building"/>. You can download
         the source code archive for this release from the MySQL FTP site
-        at
-        <ulink url="&base-url-cge-files;mysql-5.1.22-ndb-6.3.4"/>.
+        at <ulink url="&base-url-cge-files;mysql-5.1.22-ndb-6.3.4"/>.
         The file
         <filename>mysqlcom-5.1.22-ndb-6.3.4-telco.tar.gz</filename> in
         this directory contains the complete source archive.
       </para>
--->
 
       <note>
         <para role="release-non-production">

@@ -924,6 +921,111 @@
           </para>
         </listitem>
 
+        <listitem>
+          <para>
+            It was possible in some cases for a node group to be
+            <quote>lost</quote> due to missed local checkpoints
+            following a system restart. (Bug #31525)
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Cluster Replication</emphasis>: Relay
+            logs were rotated every <literal>slave_net_timeout</literal>
+            seconds even if no statements were being replicated. (Bug
+            #20435)
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <literal>NDB</literal> tables having names containing
+            non-alphanumeric characters (such as
+            <quote><literal>$</literal></quote>) were not
discovered
+            correctly. (Bug #31470)
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            A node failure during a local checkpoint could lead to a
+            subsequent failure of the cluster during a system restart.
+            (Bug #31257)
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            A cluster restart could sometimes fail due to an issue with
+            table IDs. (Bug #30975)
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <command>ndb_mgm <option>--help</option></command>
did not
+            display any information about the <option>-a</option>
+            option. (Bug #29509)
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            The cluster log was formatted inconsistently and contained
+            extraneous newline characters. (Bug #25064)
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            In some cases, the cluster managment server could log
+            entries multiple times folowing a restart of
+            <command>mgmd</command>. (Bug #29565)
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            Transaction timeouts were not handled well in some
+            circumstances, leading to excessive number of transactions
+            being aborted unnecessarily. (Bug #30379)
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            Online <literal>ALTER</literal> operations involving a
+            column whose data type has an implicit default value left
+            behind temporary <filename>.FRM</filename> files, causing
+            subsequent <literal>DROP DATABASE</literal> statements to
+            fail. (Bug #31097)
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            The <command>mysqld_safe</command> script had a syntax error
+            in a test operation. (Bug #30624)
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            Transactions were committed prematurely when <literal>LOCK
+            TABLE</literal> and <literal>SET AUTOCOMMIT=OFF</literal>
+            were used together. (Bug #30996)
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            An interpreted program of sufficient size and complexity
+            could cause all cluster data nodes to shut down due to
+            buffer overruns. (Bug #29390)
+          </para>
+        </listitem>
+
       </itemizedlist>
 
     </section>