Private/issue 10444 anti dep write skew

[ljluestc]

What problem does this PR solve?

Issue Number: ref #10444

Problem Summary:

#10444 报告了在 SELECT ... FOR UPDATE 场景下，针对不存在键可能出现反依赖环（G2）与写偏斜（A5B）异常。
本 PR 的目标是补齐并发回归测试，持续验证悲观事务 + RR 下的锁行为，避免该类问题回归。

What changed and how does it work?

本次为测试增强，不涉及生产逻辑改动，主要包括：

1. pkg/executor/test/writetest/write_test.go

• 新增 TestPessimisticForUpdateLockNonExistentKey
• 验证 point-get FOR UPDATE 在不存在键上仍形成正确阻塞与串行化

2. tests/realtikvtest/txntest/isolation_test.go

• 新增 TestG2AntiDependencyCycleForUpdate
• 新增 TestA5BWriteSkewForUpdateNonExistent
• 使用 RealTiKV 路径覆盖 Anti-dependency cycles & write skew with select ... for update #10444 场景（包含阻塞与提交顺序）

Check List

Tests

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

  • I checked and no code files have been changed.

本地验证命令与结果：

1. executor 快速回归

go test -run TestPessimisticForUpdateLockNonExistentKey -tags=intest,deadlock ./pkg/executor/test/writetest

结果：ok github.com/pingcap/tidb/pkg/executor/test/writetest

2. RealTiKV 回归

go test -run 'TestG2AntiDependencyCycleForUpdate|TestA5BWriteSkewForUpdateNonExistent' -tags=intest,deadlock ./tests/realtikvtest/txntest/...

结果：ok github.com/pingcap/tidb/tests/realtikvtest/txntest

补充说明：

• 当前环境中 make bazel_prepare 因 Bazel native thread / resource limit OOM 失败，属于环境资源限制，并非本次用例逻辑失败。

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

None

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 20ddc9e8-043f-464a-ab2d-8264fded34a2

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign qiuyesuifeng for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

Hi @ljluestc. Thanks for your PR.

I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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-sigs/prow repository.

[pingcap-cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[tiprow]

Hi @ljluestc. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Details

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-sigs/prow repository.

[ti-chi-bot]

[FORMAT CHECKER NOTIFICATION]

Notice: To remove the do-not-merge/invalid-title label, please follow title format, for example pkg [, pkg2, pkg3]: what is changed or *: what is changed.

_{📖 For more info, you can check the "Contribute Code" section in the development guide.}