| Bug #7823 | FLUSH TABLES WITH READ LOCK + INSERT DELAYED = deadlock | ||
|---|---|---|---|
| Submitted: | 12 Jan 2005 2:49 | Modified: | 28 Apr 2005 16:07 |
| Reporter: | Christopher L. Cousins | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server | Severity: | S3 (Non-critical) |
| Version: | 4.0.23 | OS: | Linux (Red Hat Enterprise Linux) |
| Assigned to: | Ingo Strüwing | CPU Architecture: | Any |
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:
- On *nix platforms use the split command e.g.
split -b 50MB <my_large_archive> <my_split_archive_prefix> - On windows use WinZip or a similar utility to split the large file
[12 Jan 2005 2:52]
Christopher L. Cousins
[12 Jan 2005 2:52]
Christopher L. Cousins
generate 'FLUSH TABLES WITH READ LOCK' SQL file
Attachment: ftwrl.py (application/octet-stream, text), 143 bytes.
[4 Feb 2005 14:37]
Ingo Strüwing
My test script. We cannot test concurrency in the normal MySQL test suite.
Attachment: bug7823-1.sh (application/x-sh, text), 5.51 KiB.
