| Bug #32416 | Foreign key constraint violation under concurrent load | ||
|---|---|---|---|
| Submitted: | 15 Nov 2007 17:15 | Modified: | 24 Jul 2008 11:57 |
| Reporter: | Fadi Bitar | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S1 (Critical) |
| Version: | 5.0.27, 5.0.37, 5.1.22 | OS: | Linux |
| Assigned to: | Vasil Dimov | CPU Architecture: | Any |
| Tags: | concurrent, foreign key, insert | ||
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
[15 Nov 2007 17:16]
Fadi Bitar
[17 Nov 2007 14:32]
Ryan Murray
innodb status after foreign key error
Attachment: inndb status output.txt (text/plain), 7.29 KiB.
[10 Apr 2008 12:16]
Fadi Bitar
Code to reproduce the bug
Attachment: mysqlbug.zip (application/x-zip-compressed, text), 2.30 KiB.
[10 Apr 2008 12:17]
Fadi Bitar
Documented reproduction procedure
Attachment: deadlock-sql.doc (application/msword, text), 30.50 KiB.
