-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
planner, sessionctx : Add 'last_plan_from_cache' to help know whether sql's plan is from plan cache #16321
Conversation
change mystmt to stmt
Co-Authored-By: Zhang Jian <zjsariel@gmail.com>
Improve the testing process.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Can we change the variable name to a simpler one, e.g, |
I also think the name of this variable is too long, renamed now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/run-all-tests |
/run-cherry-picker |
Signed-off-by: sre-bot <sre-bot@pingcap.com>
cherry pick to release-4.0 in PR #16830 |
What problem does this PR solve?
Issue Number: close #16127
Problem Summary:
What is changed and how it works?
What's Changed:
last_plan_from_cache
to help decide whether the plan cache got hit.How it Works:
Related changes
pingcap/docs
/pingcap/docs-cn
:Check List
Tests
Side effects
Release note
The default value of
last_plan_from_cache
is false. Set operations oflast_plan_from_cache
will be ignored, and a warning will be given about that.