[MDEV-30080] Wrong result with LEFT JOINs involving constant tables Created: 2022-11-23 Updated: 2023-02-10 Resolved: 2023-01-13 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Optimizer |
| Affects Version/s: | 10.5, 10.6, 10.7, 10.8, 10.9, 10.10, 10.11 |
| Fix Version/s: | 10.11.2, 10.5.19, 10.6.12, 10.7.8, 10.8.7, 10.9.5, 10.10.3 |
| Type: | Bug | Priority: | Major |
| Reporter: | Elena Stepanova | Assignee: | Michael Widenius |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | 11.0-sel | ||
| Description |
|
The expected result is (unless I'm mistaken)
so the actual result set is wrong both in the number of rows and in the values, while the COUNT result is correct. Reproducible on 10.5+. Could not reproduce on 10.4.
|
| Comments |
| Comment by Michael Widenius [ 2023-01-13 ] |
|
The reason things fails in 10.5 and above is that test_quick_select() returns -1 (impossible range) for empty tables if there are any conditions attached. This didn't happen in 10.4 as the cost for a range was more than for a table scan with 0 rows and get_key_scan_params() did not create any range plans and thus did not mark the range as impossible. The code that checked the 'impossible range' conditions did not take into account all cases of LEFT JOIN usage. Adding an extra check if the table is used with an ON condition in case of 'impossible range' fixes the issue. |