| Bug #69179 | accessing information_schema.partitions causes plans to change | ||
|---|---|---|---|
| Submitted: | 9 May 2013 4:22 | Modified: | 23 Sep 2013 15:08 |
| Reporter: | Justin Swanhart | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S2 (Serious) |
| Version: | 5.6.11, 5.5.31, 5.6.13 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | innodb, performance, statistics | ||
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
[26 May 2013 4:31]
Justin Swanhart
[27 May 2013 19:19]
Justin Swanhart
SSB schema with partitions
Attachment: ssb_schema_partitioned.sql (text/x-sql), 6.19 KiB.
[29 May 2013 8:26]
Umesh Shastry
Test case with results...
Attachment: 69179.txt (text/plain), 20.56 KiB.
[30 May 2013 5:37]
Umesh Shastry
Test case with results...
Attachment: 69179.txt (text/plain), 11.20 KiB.
