| Bug #100257 | Optimizer chooses wrong index for ORDER BY LIMIT | ||
|---|---|---|---|
| Submitted: | 20 Jul 2020 3:57 | Modified: | 28 Jul 2020 2:27 |
| Reporter: | Matias Sánchez | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: Optimizer | Severity: | S4 (Feature request) |
| Version: | 8.0.21 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | limit, Optimizer, order by | ||
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
[20 Jul 2020 4:07]
Matias Sánchez
[20 Jul 2020 4:08]
Matias Sánchez
Optimizer trace when not using index for order by (FULL SCAN)
Attachment: wrong_plan.txt (text/plain), 17.20 KiB.
