sql/stats: remove NumRange-stealing behavior from histogram prediction #86348
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
We should be able to handle NumEq=0 just fine everywhere that uses histograms, so delete this NumRange-stealing code. Fixes: cockroachdb#86344 Release justification: low-risk updates to new functionality. Release note: None
|
This change is |
yuzefovich
approved these changes
Aug 17, 2022
There was a problem hiding this comment.
LGTM but it'd probably be good for @rytaft to sign off too.
Reviewed 4 of 4 files at r1, all commit messages.
Reviewable status:complete! 0 of 0 LGTMs obtained (waiting on @cucaroach)
rytaft
approved these changes
Aug 18, 2022
There was a problem hiding this comment.
Reviewed 4 of 4 files at r1, all commit messages.
Reviewable status:
|
TFTRs! bors r=yuzefovich,rytaft |
|
Build succeeded: |
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.
We should be able to handle NumEq=0 just fine everywhere that uses
histograms, so delete this NumRange-stealing code.
Fixes: #86344
Release justification: low-risk updates to new functionality.
Release note: None