Author: paul
Date: 2010-12-20 15:49:01 +0100 (Mon, 20 Dec 2010)
New Revision: 24506
Log:
r43306@dhcp-213: paul | 2010-12-20 08:40:53 -0500
Revise some changelog entries
Modified:
trunk/dynamic-docs/changelog/mysqld-2.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:35498
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:45597
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:66486
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546
ebeeeee4-b232-4669-a521-231442eced53:/mysqldoc-local/mysqldoc/trunk:43294
+ 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:35498
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:45597
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:66486
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546
ebeeeee4-b232-4669-a521-231442eced53:/mysqldoc-local/mysqldoc/trunk:43306
Modified: trunk/dynamic-docs/changelog/mysqld-2.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-2.xml 2010-12-20 03:30:00 UTC (rev 24505)
+++ trunk/dynamic-docs/changelog/mysqld-2.xml 2010-12-20 14:49:01 UTC (rev 24506)
Changed blocks: 4, Lines Added: 55, Lines Deleted: 17; 4443 bytes
@@ -35029,7 +35029,7 @@
<message>
<para>
- After creating a table with two foreign key constraints, the
+ After creation of a table with two foreign key constraints, the
<literal role="is">INFORMATION_SCHEMA.REFERENTIAL_CONSTRAINTS</literal>
table displayed only one of them.
</para>
@@ -35318,14 +35318,15 @@
<message>
<para>
- Deadlock occurred when a connection that had some table open
- through a <literal role="stmt">HANDLER</literal> statement tried
- to update data through a DML statement while another connection
- tried to execute <literal role="stmt" condition="flush">FLUSH
- TABLES WITH READ LOCK</literal> concurrently. Starvation of
+ Starvation of <literal role="stmt" condition="flush">FLUSH
+ TABLES WITH READ LOCK</literal> statements occurred when there
+ was a constant load of concurrent DML statements in two or more
+ connections. Deadlock occurred when a connection that had some
+ table open through a <literal role="stmt">HANDLER</literal>
+ statement tried to update data through a DML statement while
+ another connection tried to execute
<literal role="stmt" condition="flush">FLUSH TABLES WITH READ
- LOCK</literal> statements occurred when there was a constant
- load of concurrent DML statements in two or more connections.
+ LOCK</literal> concurrently.
</para>
<para>
@@ -35339,10 +35340,11 @@
<listitem>
<para>
To solve deadlock in event-handling code that was exposed by
- this patch, the LOCK_event_metadata mutex was replaced with
- metadata locks on events. As a result, DDL operations on
- events are now prohibited under <literal role="stmt">LOCK
- TABLES</literal>. This is an incompatible change.
+ this patch, the <literal>LOCK_event_metadata</literal> mutex
+ was replaced with metadata locks on events. As a result, DDL
+ operations on events are now prohibited under
+ <literal role="stmt">LOCK TABLES</literal>. This is an
+ incompatible change.
</para>
</listitem>
@@ -35365,12 +35367,48 @@
<listitem>
<para>
- Thread state names are now either <literal>Waiting for
- global read lock</literal> or <literal>Waiting for commit
- lock</literal>, depending on which stage
- <literal role="stmt" condition="flush">FLUSH TABLES WITH
- READ LOCK</literal> is in.
+ The set of thread states has changed:
</para>
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>Waiting for global metadata lock</literal> is
+ replaced by <literal>Waiting for global read
+ lock</literal>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Previously, <literal>Waiting for release of
+ readlock</literal> and <literal>Waiting to get
+ readlock</literal> were used to indicate that DML/DDL
+ was waiting for release of a read lock, Now
+ <literal>Waiting for global read lock</literal> is used.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Previously, <literal>Waiting for release of
+ readlock</literal> and <literal>Waiting for all running
+ commits to finish</literal> were used to indicate that
+ an explicit or implicit commit was waiting for release
+ of a read lock, Now <literal>Waiting for commit
+ lock</literal> is used.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ There are two other new states, <literal>Waiting for
+ trigger metadata lock</literal> and <literal>Waiting for
+ event metadata lock</literal>.
+ </para>
+ </listitem>
+
+ </itemizedlist>
</listitem>
</itemizedlist>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r24506 - in trunk: . dynamic-docs/changelog | paul.dubois | 20 Dec |
