| Bug #71849 | memory leak when subquery using order by(make_reverse) and best_key used | ||
|---|---|---|---|
| Submitted: | 26 Feb 2014 21:41 | Modified: | 4 Apr 2014 12:51 |
| Reporter: | xiaobin lin (OCA) | Email Updates: | |
| Status: | Won't fix | Impact on me: | |
| Category: | MySQL Server: Optimizer | Severity: | S3 (Non-critical) |
| Version: | 5.5 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | best_key, make_reverse, memory leak, subquery | ||
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
