-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
optimizer picks wrong driving table in nested loop join #56012
Comments
mysql> show stats_meta;
+-------------------+--------------------------+----------------+---------------------+--------------+-----------+
| Db_name | Table_name | Partition_name | Update_time | Modify_count | Row_count |
+-------------------+--------------------------+----------------+---------------------+--------------+-----------+
| test | i | | 2024-09-11 00:17:55 | 6378996 | 36 |
| test | d | | 2024-09-11 00:17:55 | 280170547 | 36 |
+-------------------+--------------------------+----------------+---------------------+--------------+-----------+ table |
replayer_OUvHRwpy4C5HFJ3gMfpyUg==_1726071458482602000.zip |
/check-issue-triage-complete |
@terry1purcell we just need to focus on the LTS version. So only need the label |
No, we won't backport this patch to lower version, because it is risky. |
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: