planner: workaround the panic of command EXECUTE when printing an expensive query log (#19316) #19339
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: ti-srebot <[email protected]>
|
/run-all-tests |
ti-srebot
added
sig/planner
|
/run-all-tests |
|
/run-check_dev |
|
/run-all-tests |
ti-srebot
added
status/LGT2
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
cherry-pick #19316 to release-3.1
What problem does this PR solve?
Issue Number: a workaround for #17419
Problem Summary:
session.currentPlanis not set when runs command EXECUTE, so that panic happens if the expensive log is printing.What is changed and how it works?
Because the fix PR #17874 has a test issue that I could not resolve quickly, so this workaround PR is filing.
Proposal: xxx
What's Changed:
How it Works:
Related changes
Check List
Tests
Side effects
Release note