| Bug #120830 | Optimizer chooses 2800x slower join order despite lower-cost JOIN_PREFIX plan | ||
|---|---|---|---|
| Submitted: | 2 Jul 3:11 | Modified: | 2 Jul 9:33 |
| Reporter: | ZHAOYANG ZHANG | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: Optimizer | Severity: | S5 (Performance) |
| Version: | 9.7.1 | OS: | Ubuntu (22.04.4 LTS) |
| Assigned to: | CPU Architecture: | x86 (x86_64, Intel(R) Xeon(R) Gold 5220) | |
| Tags: | cost, hash join, join order, JOIN_PREFIX, Optimizer, Optimizer hints, straight_join | ||
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
[2 Jul 3:13]
ZHAOYANG ZHANG
