plan, stats: fix inconsistent row count estimation #7233
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alivxxx
changed the title
alivxxx
added
component/statistics
type/enhancement
alivxxx
commented
Aug 1, 2018
statistics/selectivity.go
Outdated
| // (1): The stats type, always prefer the primary key or index. | ||
| // (2): The number of expression that it covers, the more the better. | ||
| // (3): The number of columns that it contains, the less the better. | ||
| if (bestTp == colType && set.tp < colType) || bestCount < bits || (bestCount == bits && bestNumCols > set.numCols) { |
There was a problem hiding this comment.
It is required by this PR, because after the change in logical_plans.go, it would cause failure in TestIndexRead, it would sometimes choose index (b,c).
ngaut
reviewed
Aug 1, 2018
executor/analyze.go
Outdated
| @@ -41,11 +41,13 @@ type AnalyzeExec struct { | |||
| tasks []*analyzeTask | |||
| } | |||
|
|
|||
| // MaxBucketSize is the maximum number of bucket that a histogram could contain. | |||
| var MaxBucketSize = int64(256) | |||
There was a problem hiding this comment.
This is not a good design. Do not export a variable.
winoros
reviewed
Aug 2, 2018
executor/analyze.go
Outdated
| @@ -357,3 +358,13 @@ func (e *AnalyzeColumnsExec) buildStats() (hists []*statistics.Histogram, cms [] | |||
| } | |||
| return hists, cms, nil | |||
| } | |||
|
|
|||
| // SetMaxBucketSize sets the `maxBucketSize`. | |||
| func SetMaxBucketSize(size int64) { | |||
coocood
reviewed
Aug 6, 2018
statistics/selectivity.go
Outdated
| // (1): The stats type, always prefer the primary key or index. | ||
| // (2): The number of expression that it covers, the more the better. | ||
| // (3): The number of columns that it contains, the less the better. | ||
| if (bestTp == colType && set.tp < colType) || bestCount < bits || (bestCount == bits && bestNumCols > set.numCols) { |
There was a problem hiding this comment.
I think set.tp != colType is better, because the type is not a scalar.
winoros
approved these changes
Aug 6, 2018
zhexuany
reviewed
Aug 6, 2018
| @@ -35,6 +35,8 @@ type exprSet struct { | |||
| mask int64 | |||
| // ranges contains all the ranges we got. | |||
| ranges []*ranger.Range | |||
| // numCols is the number of columns contained in the index or column(which is always 1). | |||
There was a problem hiding this comment.
If it is always 1, why don't use a const?
There was a problem hiding this comment.
It is always 1 for the column, while it could also greater than 1 for the index.
|
/run-all-tests |
alivxxx
added
status/LGT2
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What have you changed? (mandatory)
Sometimes, the estimated count of a smaller set of expression could be smaller than that of a superset, and it is not consistent. This PR fixes it by preferring the estimation of the superset because it could use more stats info.
What is the type of the changes? (mandatory)
How has this PR been tested? (mandatory)
Unit test.
Does this PR affect documentation (docs/docs-cn) update? (mandatory)
No.
Does this PR affect tidb-ansible update? (mandatory)
No.
Does this PR need to be added to the release notes? (mandatory)
No.
Refer to a related PR or issue link (optional)
Benchmark result if necessary (optional)
Add a few positive/negative examples (optional)
PTAL @coocood @zz-jason @winoros