Skip to content
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: do not acqurie pessimistic lock for non-unique index keys (#36229) #36557

Closed

Conversation

ti-srebot
Copy link
Contributor

@ti-srebot ti-srebot commented Jul 26, 2022

cherry-pick #36229 to release-5.3
You can switch your code base to this Pull Request by using git-extras:

# In tidb repo:
git pr https://github.com/pingcap/tidb/pull/36557

After apply modifications, you can push your change to this PR via:

git push git@github.com:ti-srebot/tidb.git pr/36557:release-5.3-87c5b5068ab8

Signed-off-by: ekexium eke@fastmail.com

What problem does this PR solve?

Issue Number: close #36235

Problem Summary:

Fix the condition of checking if the index KV is unique or not.

What is changed and how it works?

Check List

Tests

  • Unit test
  • Integration test
  • Manual test (add detailed scripts or steps below)
  • No code

Side effects

  • Performance regression: Consumes more CPU
  • Performance regression: Consumes more Memory
  • Breaking backward compatibility

Documentation

  • Affects user behaviors
  • Contains syntax changes
  • Contains variable changes
  • Contains experimental features
  • Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

bugfix: do not acquire pessimistic lock for non-unique index keys

Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
@ti-chi-bot
Copy link
Member

ti-chi-bot commented Jul 26, 2022

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • tiancaiamao

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@ti-chi-bot
Copy link
Member

@ti-srebot: This cherry pick PR is for a release branch and has not yet been approved by release team.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick, it must first be approved by the collaborators.

AFTER it has been approved by collaborators, please ping the release team in a comment to request a cherry pick review.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@ti-srebot
Copy link
Contributor Author

/run-all-tests

@ti-chi-bot ti-chi-bot added do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. release-note-none Denotes a PR that doesn't merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Jul 26, 2022
@ti-srebot ti-srebot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jul 26, 2022
@ti-srebot ti-srebot added this to the v5.3.1 milestone Jul 26, 2022
@ti-srebot
Copy link
Contributor Author

@ekexium you're already a collaborator in bot's repo.

@sre-bot
Copy link
Contributor

sre-bot commented Jul 26, 2022

@ti-chi-bot ti-chi-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. and removed release-note-none Denotes a PR that doesn't merit a release note. labels Jul 26, 2022
@ekexium
Copy link
Contributor

ekexium commented Sep 29, 2022

PTAL guys @tiancaiamao @wjhuang2016

@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Oct 7, 2022
@codecov
Copy link

codecov bot commented Oct 13, 2023

Codecov Report

Merging #36557 (71cdb09) into release-5.3 (e6c3d7a) will not change coverage.
Report is 36 commits behind head on release-5.3.
The diff coverage is n/a.

Additional details and impacted files
@@              Coverage Diff               @@
##           release-5.3     #36557   +/-   ##
==============================================
  Coverage      53.3571%   53.3571%           
==============================================
  Files               19         19           
  Lines             3366       3366           
==============================================
  Hits              1796       1796           
  Misses            1421       1421           
  Partials           149        149           

@ti-chi-bot ti-chi-bot closed this Dec 1, 2023
@ti-chi-bot
Copy link
Member

This pull request is closed because its related version has closed automatic cherry-picking.
If it's still needed, you can reopen it or just regenerate it using bot,
see:

https://prow.tidb.net/command-help#cherrypick
https://book.prow.tidb.net/#/plugins/cherrypicker

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/cherry-pick-not-approved release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. status/LGT1 Indicates that a PR has LGTM 1. type/5.3-cherry-pick
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants