| Bug #55832 | selects crash too easily when innodb_force_recovery>3 | ||
|---|---|---|---|
| Submitted: | 9 Aug 2010 6:32 | Modified: | 1 Dec 2010 0:36 |
| Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S1 (Critical) |
| Version: | 5.1.49, 5.5.5 | OS: | Any |
| Assigned to: | Marko Mäkelä | CPU Architecture: | Any |
| Tags: | innodb_force_recovery | ||
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
[9 Aug 2010 6:35]
Shane Bester
[9 Aug 2010 6:53]
Shane Bester
some other crashes
Attachment: bug55832_some_other_crashes.txt (text/plain), 17.43 KiB.
[11 Aug 2010 10:20]
Shane Bester
3 files. 1) valgrind output, 2) schema, 3) queries, which must be executed via "source ...." in command line client.
Attachment: bug55832.zip (application/octet-stream, text), 12.39 KiB.
[11 Aug 2010 11:52]
Marko Mäkelä
Initial patch (simple case works with innodb_force_recovery=4 or 5)
Attachment: bug55832-1.patch (text/x-diff), 3.10 KiB.
