-
Notifications
You must be signed in to change notification settings - Fork 874
Implement support for positional parameters #3852
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
Merged
Conversation
This file contains hidden or 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
vonzshik
reviewed
Jun 18, 2021
vonzshik
reviewed
Jun 18, 2021
vonzshik
approved these changes
Jun 18, 2021
This was referenced Aug 16, 2021
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.
This is an alternative, simpler approach to #3834, because of perf issues in that attempt with multiplexing. The approach here does not tie together raw SQL mode to preparation, and simply uses the presence of positional parameters as an indication that raw mode is active. In the absence of any parameters, we parse/rewrite SQL as usual, since legacy semicolon batching may be in use (
this unfortunately means that Fortunes does not work in raw mode). We may introduce a switch in the future to force raw mode, in which case the 0-param case would also not parse/rewrite.Perf-wise, the longer the SQL and the more parameters are contained, the more this will be an improvement.
Part of #1042
Leads to #2317
Detailed run results
Fortunes Before (5140019)
Fortunes After (a453dc5)
Single Query named before (5140019)
Single Query named after (a453dc5)
Single Query positional after (a453dc5)
Multi Query named before (5140019)
Multi Query named after (a453dc5)
Multi Query positional after (a453dc5)
EDIT: Note that with #3920, Fortunes can now be optimized to not parse/rewrite as well.