| Bug #104978 | Adding Join Index forces query optimizer to use inefficient execution plan | ||
|---|---|---|---|
| Submitted: | 17 Sep 2021 19:57 | Modified: | 20 Sep 2021 8:58 |
| Reporter: | Dmitrii Naumov | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: Optimizer | Severity: | S5 (Performance) |
| Version: | 8.0.26, 5.7.35 | OS: | Windows |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | execution plan, INDEX, Optimizer | ||
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
[17 Sep 2021 19:58]
Dmitrii Naumov
[17 Sep 2021 19:58]
Dmitrii Naumov
query to create tables
Attachment: CreateTables.sql (application/octet-stream, text), 318 bytes.
[17 Sep 2021 19:59]
Dmitrii Naumov
Query to generate DocumentOwner data
Attachment: DocumentOwnerData.sql (application/octet-stream, text), 45.69 KiB.
[17 Sep 2021 20:01]
Dmitrii Naumov
Script to generate Document Data Part 1
Attachment: DocumentData.sql (application/octet-stream, text), 2.30 MiB.
[17 Sep 2021 20:02]
Dmitrii Naumov
Script to generate Document Data Part 2
Attachment: DocumentData_Part2.sql (application/octet-stream, text), 2.31 MiB.
