Author: paul
Date: 2007-01-25 16:30:45 +0100 (Thu, 25 Jan 2007)
New Revision: 4639
Log:
r18805@polar: paul | 2007-01-25 09:29:12 -0600
Document bugfixes:
Bug#22868
Bug#23526
Bug#24270
Modified:
trunk/refman-4.1/news-4.0.xml
trunk/refman-4.1/news-4.1.xml
trunk/refman-5.0/releasenotes-es-5.0.xml
trunk/refman-5.1/news-5.1.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:18788
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:15249
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:13520
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:18805
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:15249
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:13520
Modified: trunk/refman-4.1/news-4.0.xml
===================================================================
--- trunk/refman-4.1/news-4.0.xml 2007-01-25 15:23:38 UTC (rev 4638)
+++ trunk/refman-4.1/news-4.0.xml 2007-01-25 15:30:45 UTC (rev 4639)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 0; 685 bytes
@@ -175,6 +175,14 @@
<listitem>
<para>
+ <literal>InnoDB</literal> exhibited thread thrashing with more
+ than 50 concurrent connections under an update-intensive
+ workload. (Bug #22868)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>InnoDB</literal> showed substandard performance with
multiple queries running concurrently. (Bug #15815)
</para>
Modified: trunk/refman-4.1/news-4.1.xml
===================================================================
--- trunk/refman-4.1/news-4.1.xml 2007-01-25 15:23:38 UTC (rev 4638)
+++ trunk/refman-4.1/news-4.1.xml 2007-01-25 15:30:45 UTC (rev 4639)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 0; 685 bytes
@@ -248,6 +248,14 @@
<listitem>
<para>
+ <literal>InnoDB</literal> exhibited thread thrashing with more
+ than 50 concurrent connections under an update-intensive
+ workload. (Bug #22868)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>InnoDB</literal> showed substandard performance with
multiple queries running concurrently. (Bug #15815)
</para>
Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml 2007-01-25 15:23:38 UTC (rev 4638)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml 2007-01-25 15:30:45 UTC (rev 4639)
Changed blocks: 10, Lines Added: 29, Lines Deleted: 21; 4848 bytes
@@ -74,17 +74,17 @@
#22646)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: The
<literal>LockPagesInMainMemory</literal> configuration
parameter has changed its type and possible values. For more
- information, see
- <literal><link
linkend="mysql-cluster-param-ndbd-definition-lockpagesinmainmemory">LockPagesInMainMemory</link></literal>.
- (Bug #25686)
+ information, see
+ <literal><link
linkend="mysql-cluster-param-ndbd-definition-lockpagesinmainmemory">LockPagesInMainMemory</link></literal>.
+ (Bug #25686)
</para>
-
+
<para>
<emphasis role="bold">Important</emphasis>: The values
<literal>true</literal> and <literal>false</literal>
are no
@@ -95,7 +95,7 @@
should instead use <literal>1</literal> to obtain the same
behavior as previously, or <literal>2</literal> to take
advantage of new functionality introduced with this release
- described in the section cited above.
+ described in the section cited above.
</para>
</listitem>
@@ -109,6 +109,14 @@
<listitem>
<para>
+ The row count for <literal>MyISAM</literal> tables was not
+ updated properly, causing <literal>SHOW TABLE STATUS</literal>
+ to report incorrect values. (Bug #23526)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
The <command>BUILD/check-cpu</command> script did not
recognize Celeron processors. (Bug #20061)
</para>
@@ -208,7 +216,7 @@
#24507)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal> (Cluster APIs): Deletion of an
@@ -216,16 +224,16 @@
long time. (Bug #25487)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: It was not possible to create
an <literal>NDB</literal> table with a key on two
<literal>VARCHAR</literal> columns where both columns had a
- storage length in excess of 256. (Bug #25746)
+ storage length in excess of 256. (Bug #25746)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: In some circumstances,
@@ -233,15 +241,15 @@
<command>mysqld</command> processes to crash. (Bug #25668)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Memory allocations for
<literal>TEXT</literal> columns were calculated incorrectly,
- resulting in space being wasted and other issues. (Bug #25562)
+ resulting in space being wasted and other issues. (Bug #25562)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: The failure of a master node
@@ -249,7 +257,7 @@
later node failures. (Bug #25554)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: The
<command>ndb_mgm</command>
@@ -257,22 +265,22 @@
certain cases. (Bug #22103)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: A node shutdown occurred if
the master failed during a commit. (Bug #25364)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Creating a non-unique index
with the <literal>USING HASH</literal> clause silently created
- an ordered index instead of issuing a warning. (Bug #24820)
+ an ordered index instead of issuing a warning. (Bug #24820)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>:
<literal>SELECT</literal>
@@ -530,7 +538,7 @@
#17044)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Hosts in clusters with a large
@@ -1556,10 +1564,10 @@
<para>
<literal>NDB Cluster</literal>: A potential memory leak in the
<literal>NDB</literal> storage engine's handling of file
- operations was uncovered. (Bug #21858)
+ operations was uncovered. (Bug #21858)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: The
<literal>HELP</literal>
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-01-25 15:23:38 UTC (rev 4638)
+++ trunk/refman-5.1/news-5.1.xml 2007-01-25 15:30:45 UTC (rev 4639)
Changed blocks: 16, Lines Added: 48, Lines Deleted: 33; 7219 bytes
@@ -249,17 +249,17 @@
removed. (Bug #22687)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: The
<literal>LockPagesInMainMemory</literal> configuration
parameter has changed its type and possible values. For more
- information, see
- <literal><link
linkend="mysql-cluster-param-ndbd-definition-lockpagesinmainmemory">LockPagesInMainMemory</link></literal>.
- (Bug #25686)
+ information, see
+ <literal><link
linkend="mysql-cluster-param-ndbd-definition-lockpagesinmainmemory">LockPagesInMainMemory</link></literal>.
+ (Bug #25686)
</para>
-
+
<para>
<emphasis role="bold">Important</emphasis>: The values
<literal>true</literal> and <literal>false</literal>
are no
@@ -270,10 +270,9 @@
should instead use <literal>1</literal> to obtain the same
behavior as previously, or <literal>2</literal> to take
advantage of new functionality introduced with this release
- described in the section cited above.
+ described in the section cited above.
</para>
</listitem>
-
</itemizedlist>
@@ -285,6 +284,22 @@
<listitem>
<para>
+ <command>mysql_install_db</command> did not create the
+ <literal>mysql.plugin</literal> table if strict SQL mode was
+ enabled. (Bug #24270)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The row count for <literal>MyISAM</literal> tables was not
+ updated properly, causing <literal>SHOW TABLE STATUS</literal>
+ to report incorrect values. (Bug #23526)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Using a view in combination with a <literal>USING</literal>
clause caused column aliases to be ignored. (Bug #25106)
</para>
@@ -812,7 +827,7 @@
with partitioned tables in general. (Bug #22634)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal> (Cluster APIs): Deletion of an
@@ -820,7 +835,7 @@
long time. (Bug #25487)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal> (Replication): Certain errors
@@ -828,7 +843,7 @@
(Bug #25755)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal> (Replication): Connecting a
@@ -838,16 +853,16 @@
<command>mysqld</command> process to crash. (Bug #25387)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal> (Replication): Connecting an
API node to the cluster during a node restart while performing
database operations could cause the restarting node to fail.
- (Bug #25329)
+ (Bug #25329)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal> (Disk Data): Following 3 or
@@ -856,15 +871,15 @@
Data tables. (Bug #25636)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal> (Disk Data): Issuing a
<literal>TRUNCATE</literal> statement on a Disk Data table
- caused the table to become an in-memory table. (Bug #25296)
+ caused the table to become an in-memory table. (Bug #25296)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal> (Disk Data): Changing a column
@@ -872,16 +887,16 @@
an in-memory table. (Bug #24667)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: It was not possible to create
an <literal>NDB</literal> table with a key on two
<literal>VARCHAR</literal> columns where both columns had a
- storage length in excess of 256. (Bug #25746)
+ storage length in excess of 256. (Bug #25746)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Hosts in clusters with a large
@@ -889,7 +904,7 @@
obtaining configuration data. (Bug #25711)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: In some circumstances,
@@ -897,7 +912,7 @@
<command>mysqld</command> processes to crash. (Bug #25668)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Non-32-bit, non-aligned
@@ -905,7 +920,7 @@
<literal>NDB</literal> tables. (Bug #25587)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Some aggregate queries such as
@@ -915,15 +930,15 @@
in MySQL Cluster 5.1 than in 5.0. (Bug #25567)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Memory allocations for
<literal>TEXT</literal> columns were calculated incorrectly,
- resulting in space being wasted and other issues. (Bug #25562)
+ resulting in space being wasted and other issues. (Bug #25562)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: The failure of a master node
@@ -931,7 +946,7 @@
later node failures. (Bug #25554)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: The failure of a node during a
@@ -939,22 +954,22 @@
#25468)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: A node shutdown occurred if
the master failed during a commit. (Bug #25364)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: Creating a non-unique index
with the <literal>USING HASH</literal> clause silently created
- an ordered index instead of issuing a warning. (Bug #24820)
+ an ordered index instead of issuing a warning. (Bug #24820)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: The
<command>ndb_mgm</command>
@@ -962,15 +977,15 @@
certain cases. (Bug #22103)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: A potential memory leak in the
<literal>NDB</literal> storage engine's handling of file
- operations was uncovered. (Bug #21858)
+ operations was uncovered. (Bug #21858)
</para>
</listitem>
-
+
<listitem>
<para>
<literal>NDB Cluster</literal>: When stopping and restarting
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r4639 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 25 Jan |