| Bug #93188 | Optimiser chose incorrect join order inside of derived table | ||
|---|---|---|---|
| Submitted: | 14 Nov 2018 11:16 | Modified: | 16 Nov 2018 14:43 |
| Reporter: | Lobanov Mikhail | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: Optimizer | Severity: | S5 (Performance) |
| Version: | 5.7 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | derived table | ||
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
[14 Nov 2018 14:57]
Lobanov Mikhail
[15 Nov 2018 14:09]
Evgeny Shichenko
Explain: temp query first in query
Attachment: explain_temp_first.json (application/json, text), 4.10 KiB.
[15 Nov 2018 14:09]
Evgeny Shichenko
Explain: ab table query first in query
Attachment: explain_ab_first.json (application/json, text), 3.93 KiB.
[15 Nov 2018 16:20]
SINISA MILIVOJEVIC
The output from EXPLAIN and the associated traces
Attachment: trace.txt (text/plain), 19.72 KiB.
[16 Nov 2018 14:41]
SINISA MILIVOJEVIC
EXPLAINs and traces for UPDATE
Attachment: trace1.txt (text/plain), 32.93 KiB.
