util: change record analyze to explain in oom alarm#39099
util: change record analyze to explain in oom alarm#39099ti-chi-bot merged 7 commits intopingcap:masterfrom
Conversation
This reverts commit d970c9b.
…n memory usage alarm (pingcap#38729)" This reverts commit ba175c4.
…gcap#38727)" This reverts commit a151383.
|
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. DetailsReviewer can indicate their review by submitting an approval review. |
|
/rebuild |
|
/run-all-tests |
|
/merge |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: 2f1d2ec |
Signed-off-by: Weizhen Wang <wangweizhen@pingcap.com>
|
/merge |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: f4daba4 |
|
In response to a cherrypick label: new pull request created: #39100. |
TiDB MergeCI notify🔴 Bad News! New failing [2] after this pr merged.
|
What problem does this PR solve?
Issue Number: close #39036 #39094 #39098
Problem Summary:
What is changed and how it works?
At present, method plannercore.GetExplainAnalyzeRowsForPlan is called only after the sql is executed
Because method plannercore.GetExplainAnalyzeRowsForPlan() was previously called only after the sql was executed, concurrency was not considered. If method plannercore.GetExplainAnalyzeRowsForPlan() is called during sql execution, there will be a lot of panic associated with concurrent map and it will be difficult to handle, so we will only record the plan to solve this problem.
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.