-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
executor: lock duplicated keys on insert-ignore & replace-nothing (#42210) #42290
executor: lock duplicated keys on insert-ignore & replace-nothing (#42210) #42290
Conversation
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
Signed-off-by: zyguan <zhongyangguan@gmail.com>
…ap#42642) ref pingcap#28011 Signed-off-by: zyguan <zhongyangguan@gmail.com>
@ekexium @MyonKeminta @you06 PTAL |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 483ffd9
|
/retest |
/retest |
/test check-dev |
This is an automated cherry-pick of #42210
What problem does this PR solve?
Issue Number: close #42121 #40461 #28011
Problem Summary: When doing insert-ingore or replace without changes, tidb doesn't lock conflict keys properly.
What is changed and how it works?
Lock keys even when insert-ingnore meets duplicated rows or replace without changes.
Check List
Tests
Side effects
The change may introduce more lock records, which may further lead performance regression like #25659 .
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.