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

[6.1] Cherry-pick changes about the fix of pessimistic transactions with primary changed #1141

Conversation

MyonKeminta
Copy link
Contributor

ref: pingcap/tidb#42937

Cherry-picks #1105 #1107 to release-6.5 branch

…ith primary changed

* Add a flag to CheckTxnStatusRequest to tell TiKV to check whether the lock on the key (if any) is a real primary lock (pingcap#1105)

Signed-off-by: MyonKeminta <MyonKeminta@users.noreply.github.com>
Co-authored-by: MyonKeminta <MyonKeminta@users.noreply.github.com>
Co-authored-by: ekexium <eke@fastmail.com>
@MyonKeminta MyonKeminta changed the base branch from master to release-6.1 June 29, 2023 10:04
@MyonKeminta MyonKeminta marked this pull request as draft June 29, 2023 12:05
@MyonKeminta
Copy link
Contributor Author

Sorry. I noticed that some released versions with larger minor version number than 6.1 (like 6.5) doesn't contain this fix. Fixing this in 6.1 branch might cause problem if there are any user trying to upgrade to older version in newer branch (such as upgrading from 6.1.7 to 6.5.0). For this reason, whether this bug should be fixed in 6.1 branch needs discussion.
cc @cfzjywxk

@cfzjywxk
Copy link
Contributor

cfzjywxk commented Jun 29, 2023

Got it,I think to keep compatibility we could skip the fix on v6.1.
Though it's a correctness risk it rarely happens.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants