-
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
planner: fix row count estimation for unique composite IndexScan of IndexJoin #14167
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/run-all-tests |
@eurekaka merge failed. |
/run-unit-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, there's some more things we should consider?
Just reviewed the codebase.
I think we need to check when the helper.maxUsedCols
is the index's full length. There still be the case that the filters on the last column is not equal condition?
@winoros OK, thanks. |
/rebuild |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
/merge |
/run-all-tests |
What problem does this PR solve?
Fix #14051
What is changed and how it works?
Fix the wrong conditions used in checking
maxOneRow
.Check List
Tests
Code changes
N/A
Side effects
N/A
Related changes
N/A
Release note
N/A