plan: do not cache plan for query on range partition table (#15697) #15749
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 #15697 to release-3.1
What problem does this PR solve?
Issue Number: close #15720
Problem Summary:
Query on range partition may return error when using prepared plan cache, because table id is written in physical plan. Some user may use partition + plan cache when TiDB 4.0-rc released. So currently let plan-cache do not cache query on range partition table.
What is changed and how it works?
Proposal: xxx
What's Changed:
Add
isRangePartition
to check whether a plan is on range partition table.How it Works:
If a plan is on range partition table, plan cache will not cache it.
Related changes
pingcap/docs
/pingcap/docs-cn
:pingcap/tidb-ansible
:Check List
Tests
Side effects
Release note