Author: paul
Date: 2007-07-30 22:12:10 +0200 (Mon, 30 Jul 2007)
New Revision: 7275
Log:
r28039@polar: paul | 2007-07-30 15:07:41 -0500
Document bugfixes:
Bug#25078
Bug#28544
Bug#29957
Bug#30084
Modified:
trunk/refman-4.1/news-4.1.xml
trunk/refman-4.1/se-innodb.xml
trunk/refman-5.0/releasenotes-cs-5.0.xml
trunk/refman-5.0/releasenotes-es-5.0.xml
trunk/refman-5.0/se-innodb.xml
trunk/refman-5.1/news-5.1.xml
trunk/refman-5.1/se-innodb.xml
trunk/refman-5.2/se-innodb.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:28038
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:23143
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:18941
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:28039
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:23143
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:18941
Modified: trunk/refman-4.1/news-4.1.xml
===================================================================
--- trunk/refman-4.1/news-4.1.xml 2007-07-30 20:11:54 UTC (rev 7274)
+++ trunk/refman-4.1/news-4.1.xml 2007-07-30 20:12:10 UTC (rev 7275)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 0; 612 bytes
@@ -201,6 +201,13 @@
<listitem>
<para>
+ On Mac OS X, shared-library installation pathnames were
+ incorrect. (Bug #28544)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
A field packet with <literal>NULL</literal> fields caused a
<literal>libmysqlclient</literal> crash. (Bug #29494)
</para>
Modified: trunk/refman-4.1/se-innodb.xml
===================================================================
--- trunk/refman-4.1/se-innodb.xml 2007-07-30 20:11:54 UTC (rev 7274)
+++ trunk/refman-4.1/se-innodb.xml 2007-07-30 20:12:10 UTC (rev 7275)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 1; 761 bytes
@@ -7401,7 +7401,11 @@
<listitem>
<para>
<literal>InnoDB</literal> has a limit of 1023 concurrent
- transactions.
+ transactions that have created undo records by modifying data.
+ Workarounds include keeping transactions as small and fast as
+ possible and delaying changes until near the end of the
+ transaction. Applications should commit transactions before
+ doing time-consuming client-side operations.
</para>
</listitem>
Modified: trunk/refman-5.0/releasenotes-cs-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-cs-5.0.xml 2007-07-30 20:11:54 UTC (rev 7274)
+++ trunk/refman-5.0/releasenotes-cs-5.0.xml 2007-07-30 20:12:10 UTC (rev 7275)
Changed blocks: 1, Lines Added: 10, Lines Deleted: 0; 880 bytes
@@ -217,6 +217,16 @@
<listitem>
<para>
+ On the IBM i5 platform, the installation script in *SAVF
+ binaries unconditionally executed the
+ <command>mysql_install_db</command> script. This problem was
+ fixed in a repackaged distribution numbered 5.0.45b. (Bug
+ #30084)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>NDB Cluster</literal>: A race condition could result
when non-master nodes (in addition to the master node) tried
to update active status due to a local checkpoint. Now only
Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml 2007-07-30 20:11:54 UTC (rev 7274)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml 2007-07-30 20:12:10 UTC (rev 7275)
Changed blocks: 4, Lines Added: 45, Lines Deleted: 0; 2773 bytes
@@ -93,6 +93,23 @@
<listitem>
<para>
+ On Mac OS X, shared-library installation pathnames were
+ incorrect. (Bug #28544)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For <literal>MyISAM</literal> tables on Windows,
+ <literal>INSERT</literal>, <literal>DELETE</literal>, or
+ <literal>UPDATE</literal> followed by <literal>ALTER
+ TABLE</literal> within <literal>LOCK TABLES</literal> could
+ cause table corruption. (Bug #29957)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
When using a <literal>FEDERATED</literal> table, the value of
<literal>last_insert_id()</literal> would not correctly update
the C API interface, which would affect the autogenerated ID
@@ -522,6 +539,14 @@
<listitem>
<para>
+ On the IBM i5 platform, the installation script in *SAVF
+ binaries unconditionally executed the
+ <command>mysql_install_db</command> script. (Bug #30084)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>NDB Cluster</literal>: The management client's
response to <literal>START BACKUP WAIT COMPLETED</literal> did
not include the backup ID. (Bug #27640)
@@ -1256,6 +1281,16 @@
<listitem>
<para>
+ On the IBM i5 platform, the installation script in *SAVF
+ binaries unconditionally executed the
+ <command>mysql_install_db</command> script. This problem was
+ fixed in a repackaged distribution numbered 5.0.44b. (Bug
+ #30084)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>NDB Cluster</literal>: A race condition could result
when non-master nodes (in addition to the master node) tried
to update active status due to a local checkpoint. Now only
@@ -2164,6 +2199,16 @@
<listitem>
<para>
+ On the IBM i5 platform, the installation script in *SAVF
+ binaries unconditionally executed the
+ <command>mysql_install_db</command> script. This problem was
+ fixed in a repackaged distribution numbered 5.0.42b. (Bug
+ #30084)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>NDB Cluster</literal>: Repeated insertion of data
generated by <command>mysqldump</command> into
<literal>NDB</literal> tables could eventually lead to failure
Modified: trunk/refman-5.0/se-innodb.xml
===================================================================
--- trunk/refman-5.0/se-innodb.xml 2007-07-30 20:11:54 UTC (rev 7274)
+++ trunk/refman-5.0/se-innodb.xml 2007-07-30 20:12:10 UTC (rev 7275)
Changed blocks: 1, Lines Added: 6, Lines Deleted: 1; 834 bytes
@@ -7520,7 +7520,12 @@
<listitem>
<para>
<literal>InnoDB</literal> has a limit of 1023 concurrent
- transactions.
+ transactions that have created undo records by modifying data.
+ Workarounds include keeping transactions as small and fast as
+ possible, delaying changes until near the end of the
+ transaction, and using stored routines to reduce client-server
+ latency delays. Applications should commit transactions before
+ doing time-consuming client-side operations.
</para>
</listitem>
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2007-07-30 20:11:54 UTC (rev 7274)
+++ trunk/refman-5.1/news-5.1.xml 2007-07-30 20:12:10 UTC (rev 7275)
Changed blocks: 2, Lines Added: 27, Lines Deleted: 0; 1462 bytes
@@ -99,6 +99,16 @@
</para>
</listitem>
+ <listitem>
+ <para>
+ The replication thread on a slave now is always allowed to
+ enter <literal>InnoDB</literal> even if this would exceed the
+ limit imposed by the
+ <literal>innodb_thread_concurrency</literal> system variable.
+ (Bug #25078)
+ </para>
+ </listitem>
+
</itemizedlist>
<para>
@@ -207,6 +217,23 @@
<listitem>
<para>
+ On Mac OS X, shared-library installation pathnames were
+ incorrect. (Bug #28544)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ For <literal>MyISAM</literal> tables on Windows,
+ <literal>INSERT</literal>, <literal>DELETE</literal>, or
+ <literal>UPDATE</literal> followed by <literal>ALTER
+ TABLE</literal> within <literal>LOCK TABLES</literal> could
+ cause table corruption. (Bug #29957)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
When determining which transaction to kill after deadlock has
been detected, <literal>InnoDB</literal> now adds the number
of locks to a transaction's weight, and avoids killing
Modified: trunk/refman-5.1/se-innodb.xml
===================================================================
--- trunk/refman-5.1/se-innodb.xml 2007-07-30 20:11:54 UTC (rev 7274)
+++ trunk/refman-5.1/se-innodb.xml 2007-07-30 20:12:10 UTC (rev 7275)
Changed blocks: 1, Lines Added: 6, Lines Deleted: 1; 834 bytes
@@ -7517,7 +7517,12 @@
<listitem>
<para>
<literal>InnoDB</literal> has a limit of 1023 concurrent
- transactions.
+ transactions that have created undo records by modifying data.
+ Workarounds include keeping transactions as small and fast as
+ possible, delaying changes until near the end of the
+ transaction, and using stored routines to reduce client-server
+ latency delays. Applications should commit transactions before
+ doing time-consuming client-side operations.
</para>
</listitem>
Modified: trunk/refman-5.2/se-innodb.xml
===================================================================
--- trunk/refman-5.2/se-innodb.xml 2007-07-30 20:11:54 UTC (rev 7274)
+++ trunk/refman-5.2/se-innodb.xml 2007-07-30 20:12:10 UTC (rev 7275)
Changed blocks: 1, Lines Added: 6, Lines Deleted: 1; 834 bytes
@@ -7517,7 +7517,12 @@
<listitem>
<para>
<literal>InnoDB</literal> has a limit of 1023 concurrent
- transactions.
+ transactions that have created undo records by modifying data.
+ Workarounds include keeping transactions as small and fast as
+ possible, delaying changes until near the end of the
+ transaction, and using stored routines to reduce client-server
+ latency delays. Applications should commit transactions before
+ doing time-consuming client-side operations.
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r7275 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-5.2 | paul | 30 Jul |
