bindinfo: avoid duplicate bindings caused by concurrent baseline capture (#22182) #22295
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 #22182 to release-4.0
You can switch your code base to this Pull Request by using git-extras:
# In tidb repo: git pr 22295
After apply modifications, you can push your change to this PR via:
What problem does this PR solve?
Issue Number: close #22178
Problem Summary:
Duplicate bindings for a same original_sql.
What is changed and how it works?
What's Changed:
Call
CreateBindRecord
instead ofAddBindRecord
inCaptureBaselines
.How it Works:
AddBindRecord
only checks the duplicate in binding cache, whileCreateBindRecord
would remove duplicate bindings inmysql.bind_info
unconditionally.Related changes
Check List
Tests
Side effects
N/A
Release note