executor: fix forget to release session

[lance6716]

What problem does this PR solve?

Issue Number: close #56271

Problem Summary:

What changed and how does it work?

Check List

Tests

• Unit test
• Integration test
• Manual test WIP
• 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.

None

[tiprow]

Hi @lance6716. 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 75.3807%. Comparing base (165c4a5) to head (1b12fc6).
Report is 271 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #56299        +/-   ##
================================================
+ Coverage   73.4181%   75.3807%   +1.9625%     
================================================
  Files          1605       1605                
  Lines        445003     445037        +34     
================================================
+ Hits         326713     335472      +8759     
+ Misses        98242      89111      -9131     
- Partials      20048      20454       +406     

Flag	Coverage Δ
integration	48.9601% <100.0000%> (?)
unit	72.4908% <100.0000%> (-0.0172%)	⬇️

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

Components	Coverage Δ
dumpling	52.9478% <ø> (ø)
parser	∅ <ø> (∅)
br	52.9295% <ø> (+6.8986%)	⬆️

[tiancaiamao]

I think it may fix #56271

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: CbcWestwolf, tiancaiamao

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 [CbcWestwolf,tiancaiamao]

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-09-25 09:37:29.755890142 +0000 UTC m=+1645119.496314080: ☑️ agreed by tiancaiamao.
• 2024-09-25 09:42:44.25930657 +0000 UTC m=+1645433.999730509: ☑️ agreed by CbcWestwolf.

[ti-chi-bot]

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

[ti-chi-bot]

In response to a cherrypick label: new pull request could not be created: failed to create pull request against pingcap/tidb#release-7.5 from head ti-chi-bot:cherry-pick-56299-to-release-7.5: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for ti-chi-bot:cherry-pick-56299-to-release-7.5."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

[ti-chi-bot]

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