Author: jstephens
Date: 2007-04-10 15:20:40 +0200 (Tue, 10 Apr 2007)
New Revision: 5799
Log:
Reformat.
Modified:
branches/telcos/refman-5.1/news-5.1.xml
Modified: branches/telcos/refman-5.1/news-5.1.xml
===================================================================
--- branches/telcos/refman-5.1/news-5.1.xml 2007-04-10 13:19:59 UTC (rev 5798)
+++ branches/telcos/refman-5.1/news-5.1.xml 2007-04-10 13:20:40 UTC (rev 5799)
Changed blocks: 6, Lines Added: 29, Lines Deleted: 29; 5449 bytes
@@ -154,7 +154,7 @@
</para>
<itemizedlist>
-
+
<listitem>
<para>
<emphasis role="bold">Cluster APIs</emphasis>: An issue with
@@ -164,27 +164,27 @@
corruption. (Bug #27663)
</para>
</listitem>
-
+
<listitem>
<para>
<emphasis role="bold">Cluster APIs</emphasis>: Using
<literal>NdbBlob::writeData()</literal> to write data in the
- middle of an existing blob value (that is, updating the value)
- could overwrite some data past the end of the data to be
- changed. (Bug #27018)
+ middle of an existing blob value (that is, updating the
+ value) could overwrite some data past the end of the data to
+ be changed. (Bug #27018)
</para>
</listitem>
-
+
<listitem>
<para>
<emphasis role="bold">Cluster Replication</emphasis>: Trying
to replicate a large number of frequent updates with a
relatively small relay log
(<literal>max-relay-log-size</literal> set to 1M or less)
- could cause the slave to crash. (Bug #27529)
+ could cause the slave to crash. (Bug #27529)
</para>
</listitem>
-
+
<listitem>
<para>
<emphasis role="bold">Cluster Replication</emphasis>: An SQL
@@ -192,50 +192,50 @@
point of failure; that is, if it failed, the replication
slave had no way of knowing this, which could result in a
mismatch of data between the master and the slave. (Bug
- #21494)
+ #21494)
</para>
</listitem>
-
+
<listitem>
<para>
Memory usage of a <command>mysqld</command> process grew
even while idle. (Bug #27560)
</para>
</listitem>
-
+
<listitem>
<para>
The Cluster table handler did not set bits in null bytes
- correctly. (Bug #26591)
+ correctly. (Bug #26591)
</para>
</listitem>
-
+
<listitem>
<para>
When trying to create tables on an SQL node not connected to
the cluster, a misleading error message <errortext>Table
- '<replaceable>tbl_name</replaceable>' already
- exists</errortext> was generated. The error now generated
- is <errortext>Could not connect to storage
- engine</errortext>. (Bug #18676)
+ '<replaceable>tbl_name</replaceable>' already
+ exists</errortext> was generated. The error now generated is
+ <errortext>Could not connect to storage engine</errortext>.
+ (Bug #18676)
</para>
</listitem>
-
+
<listitem>
<para>
Incorrect handling of fragmentation in a node takeover
during a restart could cause stale data to be copied to the
starting node, leading eventually to failure of the node.
- (Bug #27434)
+ (Bug #27434)
</para>
</listitem>
-
+
<listitem>
<para>
Incorrect handling of fragmentation in a node takeover
during a restart could cause stale data to be copied to the
starting node, leading eventually to failure of the node.
- (Bug #27434)
+ (Bug #27434)
</para>
</listitem>
@@ -1436,7 +1436,7 @@
</para>
<itemizedlist>
-
+
<listitem>
<para>
<emphasis role="bold">Cluster APIs</emphasis>: An issue with
@@ -1446,33 +1446,33 @@
corruption. (Bug #27663)
</para>
</listitem>
-
+
<listitem>
<para>
<emphasis role="bold">Cluster Replication</emphasis>: Trying
to replicate a large number of frequent updates with a
relatively small relay log
(<literal>max-relay-log-size</literal> set to 1M or less)
- could cause the slave to crash. (Bug #27529)
+ could cause the slave to crash. (Bug #27529)
</para>
</listitem>
-
+
<listitem>
<para>
Under certain rare circumstances, <literal>DROP
TABLE</literal> or <literal>TRUNCATE</literal> of an
<literal>NDB</literal> table could cause a node failure or
- forced cluster shutdown. (Bug #27581)
+ forced cluster shutdown. (Bug #27581)
</para>
</listitem>
-
+
<listitem>
<para>
Memory usage of a <command>mysqld</command> process grew
even while idle. (Bug #27560)
</para>
</listitem>
-
+
<listitem>
<para>
A data node failing while another data node was restarting
@@ -1481,7 +1481,7 @@
eventual forced shutdown of the cluster. (Bug #27466)
</para>
</listitem>
-
+
<listitem>
<para>
A data node failing while another data node was restarting
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r5799 - branches/telcos/refman-5.1 | jon | 10 Apr |
