Author: jstephens
Date: 2008-05-20 05:53:41 +0200 (Tue, 20 May 2008)
New Revision: 10780
Log:
Documented fix for Replication Bug#36197
Added 5.1.24-ndb-6.3.14 release date
Started 5.1.24-ndb-6.3.15 changelog
Modified:
trunk/dynamic-docs/changelog/mysqld-1.xml
trunk/dynamic-docs/changelog/mysqld-versions.xml
trunk/refman-5.1/mysql-cluster-news-core.xml
Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml 2008-05-20 00:55:32 UTC (rev 10779)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml 2008-05-20 03:53:41 UTC (rev 10780)
Changed blocks: 1, Lines Added: 36, Lines Deleted: 0; 1470 bytes
@@ -10,6 +10,42 @@
<tags>
<highlight type="replication"/>
+ <manual type="InnoDB"/>
+ <manual type="FLUSH TABLES"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="36197"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.24-ndb-6.2.16"/>
+ <version ver="5.1.24-ndb-6.3.15"/>
+ <version ver="5.1.25"/>
+ </versions>
+
+ <message>
+
+ <para>
+ When flushing tables, there were a slight chance that the flush
+ occurred between the processing of one table map event and the
+ next. Since the tables were opened one by one, subsequent
+ locking of tables would cause the slave to crash. This problem
+ was observed when replicating <literal>NDBCLUSTER</literal> or
+ <literal>InnoDB</literal> tables, when executing multi-table
+ updates, and when a trigger or a stored routine performed an
+ (additional) insert on a table so that two tables were
+ effectively being inserted into in the same statement.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="replication"/>
<manual type="comments"/>
<manual type="binary log"/>
</tags>
Modified: trunk/dynamic-docs/changelog/mysqld-versions.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-versions.xml 2008-05-20 00:55:32 UTC (rev 10779)
+++ trunk/dynamic-docs/changelog/mysqld-versions.xml 2008-05-20 03:53:41 UTC (rev 10780)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 1; 831 bytes
@@ -39,7 +39,8 @@
</versionentry>
<versionentry ver="5.1.24" reldate="08 April 2008"/>
- <versionentry ver="5.1.24" subver="ndb-6.3.14" reldate="Not yet released"/>
+ <versionentry ver="5.1.24" subver="ndb-6.3.15" reldate="Not yet released"/>
+ <versionentry ver="5.1.24" subver="ndb-6.3.14" reldate="11 May 2008"/>
<versionentry ver="5.1.24" subver="ndb-6.2.16" reldate="Not yet released"/>
<versionentry ver="5.1.24" subver="ndb-6.3.13" reldate="10 April 2008"/>
<versionentry ver="5.1.23" reldate="29 January 2008"/>
Modified: trunk/refman-5.1/mysql-cluster-news-core.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-news-core.xml 2008-05-20 00:55:32 UTC (rev 10779)
+++ trunk/refman-5.1/mysql-cluster-news-core.xml 2008-05-20 03:53:41 UTC (rev 10780)
Changed blocks: 3, Lines Added: 41, Lines Deleted: 30; 3221 bytes
@@ -65,6 +65,47 @@
<literal>NDBCLUSTER</literal> storage engine.
</para>
+ <section id="mysql-cluster-news-5-1-24-ndb-6-3-15">
+
+ <title condition="dynamic:changelog:vertitle" role="5.1.24-ndb-6.3.15:mysqld:all"/>
+
+ <para role="release-level">
+ This is a new Beta development release, fixing recently
+ discovered bugs and incorporating improvements made since the
+ previous &mccge-series; 6.3 release.
+ </para>
+
+ <note>
+ <para role="release-non-production">
+ Although MySQL has worked very hard to ensure a high level of
+ quality, protect your data by making a backup as you would for
+ any software beta release. Please refer to our bug database at
+ <ulink url="http://bugs.mysql.com/"/> for more details about
+ the individual bugs fixed in this version.
+ </para>
+ </note>
+
+ <para>
+ This Beta release incorporates all bugfixes and feature changes
+ made in MySQL 5.1.19-ndb-6.3.0, MySQL 5.1.19-ndb-6.3.1, MySQL
+ 5.1.22-ndb-6.3.2, MySQL 5.1.22-ndb-6.3.3, MySQL
+ 5.1.22-ndb-6.3.4, and MySQL 5.1.22-ndb-6.3.5, MySQL
+ 5.1.22-ndb-6.3.6, and MySQL 5.1.23-ndb-6.3.7, MySQL
+ 5.1.23-ndb-6.3.8, MySQL 5.1.23-ndb-6.3.9, and MySQL
+ 5.1.23-ndb-6.3.10, 5.1.23-ndb-6.3.11, and MySQL
+ 5.1.23-ndb-6.3.12, MySQL 5.1.24-ndb-6.3.13, and MySQL
+ 5.1.24-ndb-6.3.14. This release also includes all bugfixes and
+ feature enhancements that were made in the mainline MySQL
+ 5.1.21, 5.1.22, 5.1.23, and 5.1.24 releases; information about
+ these can be found in <xref linkend="news-5-1-21"/>,
+ <xref linkend="news-5-1-22"/>, <xref linkend="news-5-1-23"/>,
+ and <xref linkend="news-5-1-24"/>.
+ </para>
+
+ <para condition="dynamic:changelog:entrylist" role="5.1.24-ndb-6.3.15:mysqld:all"/>
+
+ </section>
+
<section id="mysql-cluster-news-5-1-24-ndb-6-3-14">
<title condition="dynamic:changelog:vertitle" role="5.1.24-ndb-6.3.14:mysqld:all"/>
@@ -102,21 +143,6 @@
<xref linkend="news-5-1-24"/>.
</para>
-<!--
- <important>
- <formalpara>
-
- <title>Upgrading to MySQL 5.1.18-ndb-6.2.1 from a previous release</title>
-
- <para>
-
- </para>
-
- </formalpara>
-
- </important>
- -->
-
<para condition="dynamic:changelog:entrylist" role="5.1.24-ndb-6.3.14:mysqld:all"/>
</section>
@@ -185,21 +211,6 @@
and <xref linkend="news-5-1-24"/>.
</para>
-<!--
- <important>
- <formalpara>
-
- <title>Upgrading to MySQL 5.1.18-ndb-6.2.1 from a previous release</title>
-
- <para>
-
- </para>
-
- </formalpara>
-
- </important>
- -->
-
<para condition="dynamic:changelog:entrylist" role="5.1.24-ndb-6.3.13:mysqld:all"/>
</section>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r10780 - in trunk: dynamic-docs/changelog refman-5.1 | jon | 20 May |
