Bug #48609 | deadlock when running concurrent LOCK TABLE, ALTER TABLE,DELETE LOW_PRIORITY | ||
---|---|---|---|
Submitted: | 6 Nov 2009 21:41 | Modified: | 4 Apr 2011 18:56 |
Reporter: | Matthias Leich | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | MySQL Server: Locking | Severity: | S3 (Non-critical) |
Version: | mysql-6.0-codebase-bugfixing | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | deadlock |
[6 Nov 2009 21:41]
Matthias Leich
[6 Nov 2009 21:42]
Matthias Leich
backtrace
Attachment: k1 (application/octet-stream, text), 32.18 KiB.
[20 Nov 2009 11:56]
Philip Stoev
I am setting this to Verified with the expectation that this deadlock can be debugged based on stack traces alone. If this is not the case, please set the bug back to "Need feedeback". Thank you.
[21 Jan 2010 10:12]
Konstantin Osipov
A transactional lock table issue.
[4 Apr 2011 18:56]
Dmitry Lenev
Since was bug involves WL#3561 "Transactional LOCK TABLES" and this worklog got cancelled I am closing this bug as "Won't fix".