-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
server: use stmt should apply to subsequent stmts in multi-stmt mode #26905
Conversation
[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. Reviewer can indicate their review by submitting an approval review. |
/bench |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 12c3558
|
/rebuild |
Signed-off-by: ti-srebot <[email protected]>
cherry pick to release-4.0 in PR #27394 |
Signed-off-by: ti-srebot <[email protected]>
cherry pick to release-5.0 in PR #27395 |
Signed-off-by: ti-srebot <[email protected]>
cherry pick to release-5.1 in PR #27397 |
Signed-off-by: ti-srebot <[email protected]>
cherry pick to release-5.2 in PR #27398 |
What problem does this PR solve?
Issue Number: close #26688
Problem Summary:
When multi-statement is enabled, chaining statements following a "use" stmt was not successful. i.e.
This is because of prefetching for point plans. It seems unsafe to prefetch the plan if the schema could be changed (but the query might still be valid). So my solution was to disable prefetching if there is a use stmt.
What is changed and how it works?
What's Changed:
Fixes a bug in multi-stmt mode.
Check List
Tests
Side effects
Documentation
Release note