executor: do not track membuffer's memory in executor

[ekexium]

What problem does this PR solve?

Issue Number: close #53984

Problem Summary:

What changed and how does it work?

The transaction's memory is already tracked by memdb's tracker

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.

Fix the issue that transactions' memory usage may be tracked multiple times.

[tiprow]

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

All modified and coverable lines are covered by tests ✅

Project coverage is 56.2018%. Comparing base (e985478) to head (02e3a73).
Report is 902 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #53985         +/-   ##
=================================================
- Coverage   72.8299%   56.2018%   -16.6282%     
=================================================
  Files          1531       1652        +121     
  Lines        435995     608215     +172220     
=================================================
+ Hits         317535     341828      +24293     
- Misses        98818     243044     +144226     
- Partials      19642      23343       +3701     

Flag	Coverage Δ
integration	37.3479% <ø> (?)
unit	53.5951% <ø> (-18.2288%)	⬇️

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

Components	Coverage Δ
dumpling	52.9656% <ø> (ø)
parser	∅ <ø> (∅)
br	52.7646% <ø> (+6.6281%)	⬆️

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cfzjywxk, you06

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 [cfzjywxk,you06]

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-06-24 11:20:32.975581139 +0000 UTC m=+632159.461069973: ☑️ agreed by cfzjywxk.
• 2024-07-02 06:21:46.854652953 +0000 UTC m=+1305433.340141785: ☑️ agreed by you06.

[tiprow]

@ekexium: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
fast_test_tiprow	faf34a0	link	true	/test fast_test_tiprow
tidb_parser_test	faf34a0	link	true	/test tidb_parser_test

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[ekexium]

/retest

[tiprow]

@ekexium: 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.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #54578.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.1: #55037.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #55627.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #56898.