optimizer picks wrong driving table in nested loop join #56012
Labels
may-affects-5.4
This bug maybe affects 5.4.x versions.
may-affects-6.1
may-affects-6.5
may-affects-7.1
may-affects-7.5
may-affects-8.1
severity/major
sig/planner
SIG: Planner
type/bug
The issue is confirmed as a bug.
Bug Report
1. Minimal reproduce step (Required)
2. What did you expect to see? (Required)
Execution plan should use index nested loop join on table
d
because there is a where predicate on an indexed column on tablei
.3. What did you see instead (Required)
4. What is your TiDB version? (Required)
mysql> select @@Version;
+--------------------+
| @@Version |
+--------------------+
| 8.0.11-TiDB-v7.5.1 |
+--------------------+
1 row in set (0.00 sec)
The text was updated successfully, but these errors were encountered: