| Bug #15550 | mysqld crashes in printing a FOREIGN KEY error in InnoDB | ||
|---|---|---|---|
| Submitted: | 7 Dec 2005 12:23 | Modified: | 18 Jun 2010 2:02 |
| Reporter: | Kai Ruhnau | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S1 (Critical) |
| Version: | 5.0.3 and later | OS: | Linux (Gentoo Linux) |
| Assigned to: | 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
[7 Dec 2005 12:23]
Kai Ruhnau
[8 Dec 2005 12:38]
Kai Ruhnau
gdb backtrace
Attachment: gdb back trace.txt (text/plain), 10.70 KiB.
[9 Dec 2005 7:52]
Marko Mäkelä
Preliminary patch to fix Bug #15550 in MySQL 5.0
Attachment: bug15550.patch (text/x-patch), 3.03 KiB.
[9 Dec 2005 12:23]
Marko Mäkelä
One-line patch to fix Bug #15550, and more test cases
Attachment: bug15550-2.patch (text/x-patch), 3.72 KiB.
