Bug #114 Bug in LOCK TABLE followed by DROP TABLE
| Submitted: | 2 Mar 2003 9:30 | Modified: | 3 Mar 2003 11:05 |
|---|---|---|---|
| Reporter: | Peter Zaitsev (Basic Quality Contributor) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server | Severity: | S3 (Non-critical) |
| Version: | 3.23 and 4.0 | OS: | |
| Assigned to: | Michael Widenius | CPU Architecture: | Any |
[2 Mar 2003 9:30]
Peter Zaitsev
[3 Mar 2003 7:58]
MySQL Verification Team
A bug is fixed in 3.23.56, and a fix will be merged in 4.0.12 A patch is too large for this database.
[3 Mar 2003 11:05]
Michael Widenius
Thank you for your bug report. This issue has been fixed in the latest
development tree for that product. You can find more information about
accessing our development trees at
http://www.mysql.com/doc/en/Installing_source_tree.html
This bug was not fixed by the LOCK TABLE patch we added to 3.23.
To fix this problem we had to introduce new ways to abort locks that we don't want to introduce in the stable 3.23 branch.
In other words, this bug is fixed in the 4.0 tree but will not be fixed in 3.23. I will update the manual to reflect this.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.050 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.