-
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
IndexLookUp cost mismatches actual execution time compared with TableScan by clustered index #49901
Comments
/type regression |
/type performance |
Regression Analysis |
explain analyze select * from sbtest1 where id=1 and id_1=1; |
8b06ef2 seems to be the first commit causing the plan change. mysql> select tidb_version(); id estRows actRows task access object execution info operator info memory disk |
The -1 commit seems to be fine. mysql> select tidb_version(); id estRows actRows task access object execution info operator info memory disk |
/affect 6.5 |
/label affects-6.5 |
/found customer |
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
(1) Create a sysbench table like this:
(2) Run insert.sh to insert some rows.
(3) Execute the following sqls:
(4) Compare the following plans:
2. What did you expect to see? (Required)
Execution plan uses clustered index.
3. What did you see instead (Required)
The plan uses IndexRangeScan and IndexLookUp.
4. What is your TiDB version? (Required)
v7.1.2
The text was updated successfully, but these errors were encountered: