*: fix data race in ProcessInfo

[wshwsh12]

What problem does this PR solve?

Issue Number: close #45126

Problem Summary:

What is changed and how it works?

Clone some fields from stmtContext to ProcessInfo.

Check List

Tests

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

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 @wshwsh12. 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/test-infra repository.

[jackysp]

I just want to know that why #39368 could not avoid this data race.

[wshwsh12]

I just want to know that why #39368 could not avoid this data race.

#39368 avoid data race from the function (s *SessionVars).InitStatementContext by calling s.RefCountOfStmtCtx.TryFreeze()
If you want to use RefCountOfStmtCtx to avoid this data race, we need call s.RefCountOfStmtCtx.TryFreeze() in some functions in builder.go file.

[hawkingrei]

/lgtm

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2023-07-03 10:14:43.500054005 +0000 UTC m=+26115.433687427: ☑️ agreed by XuHuaiyu.
• 2023-07-05 06:36:29.916755513 +0000 UTC m=+185821.850388996: ☑️ agreed by hawkingrei.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hawkingrei, XuHuaiyu

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 [XuHuaiyu,hawkingrei]

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

[tiprow]

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

Test name	Commit	Details	Required	Rerun command
tiprow_fast_test	f18f0ff	link	true	/test tiprow_fast_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/test-infra repository. I understand the commands that are listed here.

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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