perf: use last_statement optimization in autocommit #1911
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
product-auto-label
bot
added
size: m
product-auto-label
bot
added
size: xl
Statements that are executed in autocommit mode should use the last_statement optimization.
olavloite
force-pushed
the
last-statement
branch
from
dd1485b to
cdd9cbf
Compare
product-auto-label
bot
added
size: m
olavloite
force-pushed
the
last-statement
branch
from
cdd9cbf to
7e7c54c
Compare
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.
Statements that are executed in autocommit mode should use the last_statement optimization. This reduces the number of validations that Spanner executes after executing the statement, which again reduces the overall execution time of DML statements that are executed in autocommit mode.