-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
Inaccurate display of estimated row count in index join innner side #44802
Labels
may-affects-5.1
This bug maybe affects 5.1.x versions.
may-affects-5.2
This bug maybe affects 5.2.x versions.
may-affects-5.3
This bug maybe affects 5.3.x versions.
may-affects-5.4
This bug maybe affects 5.4.x versions.
may-affects-6.1
may-affects-6.5
may-affects-7.1
severity/major
sig/planner
SIG: Planner
type/bug
The issue is confirmed as a bug.
Comments
The above display problem may be introduce by #38188 in v6.4.0. However, there is still an actual inaccurate estimation issue in current LTS versions, which may cause higher estimated cost for index join. For example:
|
Another case
|
Fixed by #44865 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
may-affects-5.1
This bug maybe affects 5.1.x versions.
may-affects-5.2
This bug maybe affects 5.2.x versions.
may-affects-5.3
This bug maybe affects 5.3.x versions.
may-affects-5.4
This bug maybe affects 5.4.x versions.
may-affects-6.1
may-affects-6.5
may-affects-7.1
severity/major
sig/planner
SIG: Planner
type/bug
The issue is confirmed as a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
sbtest1
andsbtest2
using sysbench2. What did you expect to see? (Required)
The estRows of IndexRangeScan_23 is 99 rows as actRows.
3. What did you see instead (Required)
The estRows of IndexRangeScan_23 is 100000 as many as table row count.
4. What is your TiDB version? (Required)
master
The text was updated successfully, but these errors were encountered: