planner/core: support partition pruning for partition expression floor(unix_timestamp()) (#16402) #16522
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.
cherry-pick #16402 to release-3.1
What problem does this PR solve?
Issue Number: close #16354
Problem Summary:
Support partition pruning for
floor(unix_timestamp()
What is changed and how it works?
What's Changed:
Take function
floor(unix_timestamp())
as monotoneIncFuncs, special handle for this case.How it Works:
If the partition function is monotoneous, i.e.
That partition function can be used by the partition pruning algorithm.
If we view
floor(unix_timestamp())
as a single function, it basicly conform to the definition.Related changes
pingcap/docs
/pingcap/docs-cn
:pingcap/tidb-ansible
:Check List
Tests
Release note