Author: paul
Date: 2006-01-21 20:00:50 +0100 (Sat, 21 Jan 2006)
New Revision: 969
Log:
r6523@frost: paul | 2006-01-21 12:08:34 -0600
Attempt to fix bug description.
Modified:
trunk/
trunk/refman-4.1/functions.xml
trunk/refman-5.0/functions.xml
trunk/refman-5.1/functions.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6519
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2396
+ b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6523
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2396
Modified: trunk/refman-4.1/functions.xml
===================================================================
--- trunk/refman-4.1/functions.xml 2006-01-21 07:19:31 UTC (rev 968)
+++ trunk/refman-4.1/functions.xml 2006-01-21 19:00:50 UTC (rev 969)
@@ -13439,13 +13439,11 @@
</para>
<para>
- Note: If the client that holds the lock for a name
- terminates abnormally such that it does not close its
- connection to the MySQL server, the server might not notice
- for a long time that the connection has become invalid.
- Until it does notice (at which time it releases the lock),
- other clients are prevented from acquiring a lock for the
- same name. This is a known bug.
+ Note: If a client attempts to acquire a lock that is already
+ held by another client, it blocks according to the
+ <replaceable>timeout</replaceable> argument. If the blocked
+ client terminates, its thread does not die until the lock
+ request times out. This is a known bug.
</para>
</listitem>
Modified: trunk/refman-5.0/functions.xml
===================================================================
--- trunk/refman-5.0/functions.xml 2006-01-21 07:19:31 UTC (rev 968)
+++ trunk/refman-5.0/functions.xml 2006-01-21 19:00:50 UTC (rev 969)
@@ -13468,13 +13468,11 @@
</para>
<para>
- Note: If the client that holds the lock for a name
- terminates abnormally such that it does not close its
- connection to the MySQL server, the server might not notice
- for a long time that the connection has become invalid.
- Until it does notice (at which time it releases the lock),
- other clients are prevented from acquiring a lock for the
- same name. This is a known bug.
+ Note: If a client attempts to acquire a lock that is already
+ held by another client, it blocks according to the
+ <replaceable>timeout</replaceable> argument. If the blocked
+ client terminates, its thread does not die until the lock
+ request times out. This is a known bug.
</para>
</listitem>
Modified: trunk/refman-5.1/functions.xml
===================================================================
--- trunk/refman-5.1/functions.xml 2006-01-21 07:19:31 UTC (rev 968)
+++ trunk/refman-5.1/functions.xml 2006-01-21 19:00:50 UTC (rev 969)
@@ -13856,13 +13856,11 @@
</para>
<para>
- Note: If the client that holds the lock for a name
- terminates abnormally such that it does not close its
- connection to the MySQL server, the server might not notice
- for a long time that the connection has become invalid.
- Until it does notice (at which time it releases the lock),
- other clients are prevented from acquiring a lock for the
- same name. This is a known bug.
+ Note: If a client attempts to acquire a lock that is already
+ held by another client, it blocks according to the
+ <replaceable>timeout</replaceable> argument. If the blocked
+ client terminates, its thread does not die until the lock
+ request times out. This is a known bug.
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r969 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 21 Jan |
