| Bug #36681 | Insufficient plans for huge tables | ||
|---|---|---|---|
| Submitted: | 13 May 2008 8:11 | Modified: | 3 Oct 2009 18:50 |
| Reporter: | Yasufumi Kinoshita | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Server: Optimizer | Severity: | S3 (Non-critical) |
| Version: | 5.0.54 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | Contribution | ||
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
[13 May 2008 8:12]
Yasufumi Kinoshita
[14 May 2008 3:22]
Yasufumi Kinoshita
suggested
Attachment: suggested_fix_results.pdf (application/pdf, text), 9.00 KiB.
[26 May 2008 2:12]
Yasufumi Kinoshita
new results (InnoDB & MyISAM)
Attachment: suggested_fix_results_new.pdf (application/pdf, text), 11.74 KiB.
[28 May 2008 6:27]
Yasufumi Kinoshita
The same suggested fix for 5.1
Attachment: mysql-5.1.24_fix_optimizer.patch (text/x-patch), 7.15 KiB.
[28 May 2008 6:28]
Yasufumi Kinoshita
5.1 results (InnoDB & MyISAM)
Attachment: suggested_fix_results_5.1.pdf (application/pdf, text), 11.73 KiB.
