Bug #11934 FLUSH TABLES WITH READ LOCK hangs client
Submitted: 14 Jul 2005 13:53 Modified: 3 Aug 2005 18:12
Reporter: Disha
Status: Closed
Category:Server: Optimizer Severity:S2 (Serious)
Version:5.0.7-beta-nt/5.0.10 BK OS:Any (any)
Assigned to: Evgeny Potemkin Target Version:

[14 Jul 2005 13:53] Disha 
Description:
Repeating command FLUSH TABLES WITH READ LOCK hangs client instance

How to repeat:
1. delimiter//
2. Execute following statments

	FLUSH TABLES WITH READ LOCK //

	FLUSH TABLES WITH READ LOCK //

Expected Results: 
	Query OK, 0 rows affected (0.00 sec)

Actual Results: 
	Client hangs on second execution.
[14 Jul 2005 16:10] Miguel Solorzano 
Tested also on Linux and version.
[2 Aug 2005 20:04] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/internals/27801
[2 Aug 2005 20:06] Evgeny Potemkin 
When second FLUSH TABLES WITH READ LOCK statement tries to acquire lock acquired by first
statement, error is generated but ignored by server. So no OK nor ERROR is sent to
client, which is causing its' hang.
[3 Aug 2005 12:03] Evgeny Potemkin 
Fixed in 5.0.11, cset 1.1917.1.1
[3 Aug 2005 18:12] Jon Stephens 
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Documented bugfix in 5.0.11 changelog. Closed.