server: add tidb_enable_shared_lock_promotion to support for share lock upgrade

[cfzjywxk]

What problem does this PR solve?

Issue Number: close #55022

Problem Summary:

1. Support tidb_enable_shared_lock_promotion to achive that the for share statements could be executed like for update statements which acquire pessimistic locks.
2. Fix serveral issues when tidb_enable_noop_functions is enabled, the behaviours of select for share are unexpected, including:

• When nowait is used, the execution is not no-op actually.
• When tidb_enable_noop_functions is set to off, the select for share DOES acquire locks, so is on.

3. Refactor the behaviours of tidb_enable_noop_functions, tidb_enabled_shared_lock_promotion and for share statements for executions with PointGet and Coprocessor pathes.

What changed and how does it work?

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.

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.

Introduce `tidb_enable_shared_lock_promotion` to support `for share` statements could be executed like `for update` statements which acquire pessimistic locks.

[tiprow]

Hi @cfzjywxk. 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.

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.

[codecov]

Codecov Report

Attention: Patch coverage is 76.92308% with 9 lines in your changes missing coverage. Please review.

Project coverage is 74.8339%. Comparing base (3357f26) to head (5715a91).
Report is 4 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #55023        +/-   ##
================================================
+ Coverage   72.8630%   74.8339%   +1.9708%     
================================================
  Files          1570       1570                
  Lines        439501     441345      +1844     
================================================
+ Hits         320234     330276     +10042     
+ Misses        99523      90819      -8704     
- Partials      19744      20250       +506     

Flag	Coverage Δ
integration	49.0120% <76.9230%> (?)
unit	71.8155% <52.7777%> (-0.0932%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	52.9567% <ø> (ø)
parser	∅ <ø> (∅)
br	52.5187% <ø> (+6.6533%)	⬆️

[joey-yez]

LGTM

[easonn7]

/approve

[BornChanger]

we need to claim tidb_enable_shared_lock_promotion will override tidb_enable_noop_functions in release notes.
others lgtm.

[qw4990]

Should we add this new variable into the Plan Cache Key? Otherwise the optimizer might reuse an old plan after switching this variable, which might cause some problem.

[qw4990]

LGTM for the optimizer part

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BornChanger, easonn7, qw4990

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [BornChanger,qw4990]
• pkg/parser/OWNERS [BornChanger]
• pkg/planner/OWNERS [qw4990]
• pkg/sessionctx/variable/OWNERS [easonn7]

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]

[LGTM Timeline notifier]

Timeline:

• 2024-08-08 06:54:25.504946491 +0000 UTC m=+507795.372045580: ☑️ agreed by BornChanger.
• 2024-08-08 09:54:20.176460006 +0000 UTC m=+518590.043559094: ☑️ agreed by qw4990.

[cfzjywxk]

/retest

[tiprow]

@cfzjywxk: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.