Author: jstephens
Date: 2008-02-12 17:16:22 +0100 (Tue, 12 Feb 2008)
New Revision: 9798
Log:
Documented CGE 6.2.12 and CGE 6.3.9 releases
Bugfixes:
Bug #28170, Bug #30172, Bug #31477, Bug #32025, Bug #33534,
Bug #33619, Bug #34046, Bug #34107, Bug #34118, Bug #34160,
Bug #34169, Bug #34216, Bug #34260, Bug #34275, Bug #34378,
Bug #34445
InnoDB again available in CGE starting with these releases (must build
--with-innodb to enable)
Modified:
trunk/dynamic-docs/changelog/mysqld-1.xml
trunk/dynamic-docs/changelog/mysqld-versions.xml
trunk/refman-5.1/news-5.1-core.xml
Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml 2008-02-12 15:44:54 UTC (rev 9797)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml 2008-02-12 16:16:22 UTC (rev 9798)
Changed blocks: 1, Lines Added: 443, Lines Deleted: 0; 8960 bytes
@@ -10,10 +10,453 @@
<tags>
<highlight type="cluster"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="34445"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.23-ndb-6.3.9"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Cluster failures could sometimes occur when performing more than
+ three parallel takeovers during node restarts or system
+ restarts.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="cluster"/>
+ <manual type="DataMemory"/>
+ <manual type="upgrades"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="34378"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.23-ndb-6.2.12"/>
+ <version ver="5.1.23-ndb-6.3.9"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Upgrades of a cluster using while a
+ <literal>DataMemory</literal> setting in excess of 16 GB caused
+ data nodes to fail.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="cluster"/>
+ <manual type="AUTOCOMMIT"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="34275"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.23-ndb-6.2.12"/>
+ <version ver="5.1.23-ndb-6.3.9"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Performing many SQL statements within a single transaction, or
+ in <literal>AUTOCOMMIT</literal> mode, on <literal>NDB</literal>
+ tables caused a memory leak in <command>mysqld</command>.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="cluster"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="34260"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.23-ndb-6.2.12"/>
+ <version ver="5..23-ndb-6.3.9"/>
+ </versions>
+
+ <message>
+
+ <para>
+ In certain rare circumstances, a race condition could occur
+ between an aborted insert and a delete leading a data node
+ crash.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="cluster"/>
+ <manual type="UPDATE"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="34216"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.23-ndb-6.2.12"/>
+ <version ver="5.1.23-ndb-6.3.9"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Multi-table updates using ordered indexes during handling of
+ node failures could cause other data nodes to fail.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="cluster"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="34160"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.23-ndb-6.2.12"/>
+ <version ver="5.1.23-ndb-6.3.9"/>
+ </versions>
+
+ <message>
+
+ <para>
+ An issue internal to the source code could periodically
+ introduce corruption of <literal>NDB</literal> tables with no
+ readily apparent cause.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="diskdata"/>
+ <highlight type="clusterreplication"/>
+ <manual type="UNIQUE"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="34118"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.23-ndb-6.2.12"/>
+ <version ver="5.1.23-ndb-6.3.9"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Statements violating unique keys on Disk Data tables (such as
+ attempting to insert <literal>NULL</literal> into a <literal>NOT
+ NULL</literal> column) could cause data nodes to fail. When the
+ statement was executed from the binlog, this could also result
+ in failure of the slave cluster.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="cluster"/>
+ <manual type="SELECT"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="34107"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.23-ndb-6.2.12"/>
+ <version ver="5.1.23-ndb-6.3.9"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Extremely long <literal>SELECT</literal> statements (where the
+ text of the statement was in excess of 50000 characters) against
+ <literal>NDB</literal> tables returned empty results.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="cluster"/>
+ <manual type="compiling"/>
+ <manual type="FreeBSD"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="34046"/>
+ <fixes bugid="34169"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.23-ndb-6.2.12"/>
+ <version ver="5.1.23-ndb-6.3.9"/>
+ </versions>
+
+ <message>
+
+ <para>
+ When configured with <literal>NDB</literal> support, MySQL
+ failed to compile on 64-bit FreeBSD systems.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="diskdata"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="33619"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.23-ndb-6.2.12"/>
+ <version ver="5.1.23-ndb-6.3.9"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Updating in-memory columns of one or more rows of Disk Data
+ table, followed by deletion of these rows and re-insertion of
+ them, caused data node failures.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="cluster"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="33534"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.23-ndb-6.2.12"/>
+ <version ver="5.1.23-ndb-6.3.9"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Statements executing multiple inserts performed poorly on
+ <literal>NDB</literal> tables having
+ <literal>AUTO_INCREMENT</literal> columns.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="cluster"/>
+ <manual type="ndb_waiter"/>
<manual type="ndb_mgmd"/>
</tags>
<bugs>
+ <fixes bugid="32025"/>
+ <seealsobug bugid="32023"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.23-ndb-6.2.12"/>
+ <version ver="5.1.23-ndb-6.3.9"/>
+ </versions>
+
+ <message>
+
+ <para>
+ The <command>ndb_waiter</command> utility polled
+ <command>ndb_mgmd</command> excessively when obtaining the
+ status of cluster data nodes.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="cluster"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="31477"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.23-ndb-6.2.12"/>
+ <version ver="5.1.23-ndb-6.3.9"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Transaction atomicity was sometimes not preserved between reads
+ and inserts under high loads.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="cluster"/>
+ <manual type="backup"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="30172"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.23-ndb-6.2.12"/>
+ <version ver="5.1.23-ndb-6.3.9"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Having tables with a great many columns could cause Cluster
+ backups to fail.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="feature">
+
+ <tags>
+ <manual type="InnoDB"/>
+ </tags>
+
+ <versions>
+ <version ver="5.1.23-ndb-6.2.12"/>
+ <version ver="5.1.23-ndb-6.3.9"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Beginning with this version, &mccge-series;
+ 6.3.<replaceable>x</replaceable> releases once again include the
+ <literal>InnoDB</literal> storage engine. In order to enable
+ <literal>InnoDB</literal>, you must configure the build using
+ <option>--with-innodb</option>.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="clusterreplication"/>
+ <manual type="replicate-ignore-db"/>
+ <manual type="mysql.ndb_apply_status"/>
+ </tags>
+
+ <bugs>
+ <fixes bugid="28170"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.23-ndb-6.2.12"/>
+ <version ver="5.1.23-ndb-6.3.9"/>
+ </versions>
+
+ <message>
+
+ <para>
+ Setting <option>--replicate-ignore-db=mysql</option> caused the
+ <literal>mysql.ndb_apply_status</literal> table not to be
+ replicated, breaking Cluster Replication.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <tags>
+ <highlight type="cluster"/>
+ <manual type="ndb_mgmd"/>
+ </tags>
+
+ <bugs>
<fixes bugid="32023"/>
</bugs>
Modified: trunk/dynamic-docs/changelog/mysqld-versions.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-versions.xml 2008-02-12 15:44:54 UTC (rev 9797)
+++ trunk/dynamic-docs/changelog/mysqld-versions.xml 2008-02-12 16:16:22 UTC (rev 9798)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 2; 1182 bytes
@@ -27,8 +27,10 @@
<versionentry ver="5.2.1" reldate="Not released"/>
<versionentry ver="5.1.24" reldate="Not yet released"/>
<versionentry ver="5.1.23" reldate="Not yet released"/>
- <versionentry ver="5.1.23" subver="ndb-6.3.9" reldate="Not yet released"/>
- <versionentry ver="5.1.23" subver="ndb-6.2.12" reldate="Not yet released"/>
+ <versionentry ver="5.1.23" subver="ndb-6.3.10" reldate="Not yet released"/>
+ <versionentry ver="5.1.23" subver="ndb-6.2.13" reldate="Not yet released"/>
+ <versionentry ver="5.1.23" subver="ndb-6.3.9" reldate="12 February 2008"/>
+ <versionentry ver="5.1.23" subver="ndb-6.2.12" reldate="12 February 2008"/>
<versionentry ver="5.1.23" subver="ndb-6.3.8" reldate="29 January 2008"/>
<versionentry ver="5.1.23" subver="ndb-6.2.11" reldate="28 January 2008"/>
<versionentry ver="5.1.23" subver="ndb-6.3.7" reldate="19 December 2007"/>
Modified: trunk/refman-5.1/news-5.1-core.xml
===================================================================
--- trunk/refman-5.1/news-5.1-core.xml 2008-02-12 15:44:54 UTC (rev 9797)
+++ trunk/refman-5.1/news-5.1-core.xml 2008-02-12 16:16:22 UTC (rev 9798)
Changed blocks: 3, Lines Added: 293, Lines Deleted: 2; 11824 bytes
@@ -62,10 +62,14 @@
&mccge-series; releases based on MySQL 5.1.23.
</para>
- <section id="news-5-1-23-ndb-6-3-8">
+ <section id="news-5-1-23-ndb-6-2-9">
- <title condition="dynamic:changelog:vertitle" role="5.1.23-ndb-6.3.8:mysqld:all"/>
+ <title condition="dynamic:changelog:vertitle" role="5.1.23-ndb-6.2.9:mysqld:all"/>
+ <remark role="TODO">
+ Replace x/y/z with appropriate numbers throughout.
+ </remark>
+
<para role="release-level">
This is a new Beta development release, fixing recently
discovered bugs.
@@ -76,8 +80,153 @@
and the tarballs have been uploaded to the FTP site.
</remark>
+ <remark role="TODO">
+ 6.1: Remove "Obtaining..." (Nokia only - no other distribution)
+ </remark>
+
<formalpara>
+ <title>Obtaining &mccge-series; 5.1.23-ndb-6.2.9</title>
+
+ <para>
+ &mccge-series; 5.1.23-ndb-6.2.9 — like all releases for
+ &mccge-series; — 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
+ source code archives for this release in two versions. The
+ version that should use depends on whether you have a
+ commercial &mccge-series; license or you wish to use
+ &mccge-series; under the GPL.
+
+ <itemizedlist>
+
+ <listitem>
+ <formalpara>
+
+ <title>Commercial users</title>
+
+ <para>
+ Download the commercial source archive from the MySQL
+ FTP site at <ulink url="&base-url-cge-files;"/>. The
+ file
+ <filename>mysql-5.1.23-ndb-6.2.9/mysqlcom-5.1.23-ndb-6.2.9-telco.tar.gz</filename>
+ in this directory contains the complete commercial
+ source archive.
+ </para>
+
+ </formalpara>
+
+ <important>
+ <para>
+ The commercial &mccge-series; sources contain non-GPL
+ libraries and header files. <emphasis>You must not use
+ the commercial version without a commercial license
+ from MySQL AB</emphasis>. See
+ <ulink url="http://www.mysql.com/products/database/clustercge/"/>
+ for information about licensing &mccge-series; for
+ commerical use.
+ </para>
+ </important>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+
+ <title>GPL users</title>
+
+ <para>
+ If you wish to use &mccge-series; under the GPL, you
+ can obtain the GPL source tarball from the MySQL FTP
+ site at <ulink url="&base-url-cge-files;"/>. The file
+ <filename>mysql-5.1.23-ndb-6.2.9/mysql-5.1.23-ndb-6.2.9-telco.tar.gz</filename>
+ in this directory contains the complete GPL source
+ archive.
+ </para>
+
+ </formalpara>
+
+ <para>
+ You can also obtain the latest GPL &mccge-series;
+ sources from <ulink url="http://mysql.bkbits.net/"/>
+ using the free BitKeeper client. See
+ <xref linkend="installing-source-tree"/>, for more
+ information.
+ </para>
+
+ <important>
+ <para>
+ The GPL &mccge-series; sources contain GPL libraries
+ and header files. <emphasis>You must not use the GPL
+ version in applications that are not released under
+ the GPL or a GPL-compatible license</emphasis>. See
+ <ulink url="http://www.mysql.com/company/legal/licensing/foss-exception.html"/>,
+ for a list of GPL-compatible licenses.
+ </para>
+ </important>
+ </listitem>
+
+ </itemizedlist>
+ </para>
+
+ </formalpara>
+
+ <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>
+
+ <remark role="TODO">
+ Update the following paragraph to include relevant versions.
+ </remark>
+
+ <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, and MySQL
+ 5.1.23-ndb-6.3.8 as well as all bugfixes and feature changes
+ which were added in the mainline 5.1.21 and 5.1.22 releases;
+ information about these can be found in
+ <xref linkend="news-5-1-21"/> and <xref linkend="news-5-1-22"/>.
+ </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.23-ndb-6.2.9:mysqld:all"/>
+
+ </section>
+
+ <section id="news-5-1-23-ndb-6-3-8">
+
+ <title condition="dynamic:changelog:vertitle" role="5.1.23-ndb-6.3.8:mysqld:all"/>
+
+ <para role="release-level">
+ This is a new Beta development release, fixing recently
+ discovered bugs.
+ </para>
+
+ <formalpara>
+
<title>Obtaining &mccge-series; 5.1.23-ndb-6.3.8</title>
<para>
@@ -345,6 +494,148 @@
</section>
+ <section id="news-5-1-23-ndb-6-2-12">
+
+ <title condition="dynamic:changelog:vertitle" role="5.1.23-ndb-6.2.12:mysqld:all"/>
+
+ <para role="release-level">
+ This is a new Beta development release, fixing recently
+ discovered bugs.
+ </para>
+
+ <formalpara>
+
+ <title>Obtaining &mccge-series; 5.1.23-ndb-6.2.12</title>
+
+ <para>
+ &mccge-series; 5.1.23-ndb-6.2.12 — like all releases for
+ &mccge-series; — 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
+ source code archives for this release in two versions. The
+ version that should use depends on whether you have a
+ commercial &mccge-series; license or you wish to use
+ &mccge-series; under the GPL.
+
+ <itemizedlist>
+
+ <listitem>
+ <formalpara>
+
+ <title>Commercial users</title>
+
+ <para>
+ Download the commercial source archive from the MySQL
+ FTP site at <ulink url="&base-url-cge-files;"/>. The
+ file
+ <filename>mysql-5.1.23-ndb-6.2.12/mysqlcom-5.1.23-ndb-6.2.12-telco.tar.gz</filename>
+ in this directory contains the complete commercial
+ source archive.
+ </para>
+
+ </formalpara>
+
+ <important>
+ <para>
+ The commercial &mccge-series; sources contain non-GPL
+ libraries and header files. <emphasis>You must not use
+ the commercial version without a commercial license
+ from MySQL AB</emphasis>. See
+ <ulink url="http://www.mysql.com/products/database/clustercge/"/>
+ for information about licensing &mccge-series; for
+ commerical use.
+ </para>
+ </important>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+
+ <title>GPL users</title>
+
+ <para>
+ If you wish to use &mccge-series; under the GPL, you
+ can obtain the GPL source tarball from the MySQL FTP
+ site at <ulink url="&base-url-cge-files;"/>. The file
+ <filename>mysql-5.1.23-ndb-6.2.12/mysql-5.1.23-ndb-6.2.12-telco.tar.gz</filename>
+ in this directory contains the complete GPL source
+ archive.
+ </para>
+
+ </formalpara>
+
+ <para>
+ You can also obtain the latest GPL &mccge-series;
+ sources from <ulink url="http://mysql.bkbits.net/"/>
+ using the free BitKeeper client. See
+ <xref linkend="installing-source-tree"/>, for more
+ information.
+ </para>
+
+ <important>
+ <para>
+ The GPL &mccge-series; sources contain GPL libraries
+ and header files. <emphasis>You must not use the GPL
+ version in applications that are not released under
+ the GPL or a GPL-compatible license</emphasis>. See
+ <ulink url="http://www.mysql.com/company/legal/licensing/foss-exception.html"/>,
+ for a list of GPL-compatible licenses.
+ </para>
+ </important>
+ </listitem>
+
+ </itemizedlist>
+ </para>
+
+ </formalpara>
+
+ <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.18-ndb-6.2.1, MySQL 5.1.18-ndb-6.2.2 (see
+ <xref linkend="news-5-1-18-cge"/>), MySQL 5.1.19-ndb-6.2.3,
+ MySQL 5.1.19-ndb-6.2.4, MySQL 5.1.22-ndb-6.2.5, MySQL
+ 5.1.22-ndb-6.2.6, MySQL 5.1.22-ndb-6.2.7, MySQL
+ 5.1.22-ndb-6.2.8, MySQL 5.1.23-ndb-6.2.9, MySQL
+ 5.1.23-ndb-6.2.10, and MySQL 5.1.23-ndb-6.2.11, as well as all
+ bugfixes and feature changes which were added in the mainline
+ 5.1.20, 5.1.21, 5.1.22, and 5.1.23 releases; information about
+ these can be found in <xref linkend="news-5-1-20"/>,
+ <xref linkend="news-5-1-21"/><xref linkend="news-5-1-22"/>, and
+ <xref linkend="news-5-1-23"/>. Also included are most (but not
+ all) bugfixes made in the MCCGE 6.1.<replaceable>x</replaceable>
+ series through MySQL 5.1.15-ndb-6.1.16.
+ </para>
+
+<!--
+ <important>
+ <formalpara>
+
+ <title>Upgrading to MySQL 5.1.23-ndb-6.2.10 from a previous release</title>
+
+ <para>
+
+ </para>
+
+ </formalpara>
+
+ </important>
+ -->
+
+ <para condition="dynamic:changelog:entrylist" role="5.1.23-ndb-6.2.12:mysqld:all"/>
+
+ </section>
+
<section id="news-5-1-23-ndb-6-2-11">
<title condition="dynamic:changelog:vertitle" role="5.1.23-ndb-6.2.11:mysqld:all"/>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r9798 - in trunk: dynamic-docs/changelog refman-5.1 | jon | 12 Feb |
