-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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: revert #25730 to fix #28011 (#42488) #42503
executor: revert #25730 to fix #28011 (#42488) #42503
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>
/merge |
This pull request has been accepted and is ready to merge. Commit hash: d2a220d
|
/retest |
/retest |
…42488) (pingcap#42503)" This reverts commit 6211ae6.
…42488) (pingcap#42503)" This reverts commit 6211ae6.
This is an automated cherry-pick of #42488
What problem does this PR solve?
Issue Number: close #28011
Problem Summary: as described in #28011 , kv pairs converted from locks is visible to union-scan, which leads to duplicated rows (one from snapshot and the other from mem-index-reader).
What is changed and how it works?
Since tikv/tikv#13694 has introduced a better solution to the problem of accumulated locks, thus we can simply revert #25730 .
Here is the benchmark result. It shows that there is a slight regression in point-get workload.
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.