Bug #54436 Deadlock on concurrent FLUSH WITH READ LOCK, ALTER TABLE, ANALYZE TABLE
Submitted: 11 Jun 2010 16:55 Modified: 17 Mar 2011 19:04
Reporter: Matthias Leich Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Server: Locking Severity:S3 (Non-critical)
Version:5.1.38-bzr, mysql-trunk-runtime OS:Any
Assigned to: CPU Architecture:Any
Tags: deadlock

File: Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

[11 Jun 2010 17:10] Matthias Leich
RQG output with backtrace

Attachment: deadlock.prt (application/octet-stream, text), 73.60 KiB.