| Bug #79617 | Foreign key causing deadlock for UPDATE together with simple transaction | ||
|---|---|---|---|
| Submitted: | 12 Dec 2015 15:16 | Modified: | 12 Dec 2019 20:36 |
| Reporter: | David Raimosson | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Locking | Severity: | S3 (Non-critical) |
| Version: | 8.0.18 | OS: | Windows (10) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | deadlock, foreign key, innodb | ||
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 Dec 2015 15:19]
David Raimosson
[5 Feb 2016 19:38]
Jeffery Kuhn
What is the status on the fix for this bug? I seem to be having the same issue in a customer's environment. File attached.
Attachment: 27Jan_deadlock_BUG79617.log (application/octet-stream, text), 11.91 KiB.
