-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
76792: sql: use an implicit txn during the extended protocol r=otan a=rafiss fixes #71665 In the Postgres wire protocol, entering the extended protocol also starts an implicit transaction. This transaction is committed when the Sync message is received. Previously, we were starting 3 separate "implicit" transactions for the Prepare, Bind, and ExecPortal commands. (Implicit is in scare quotes because they were created entirely ad-hoc.) Now, the same implicit txn is used for the duration of the extended protocol. If BEGIN is executed as a prepared statement, then the implicit trasnaction is upgraded to an explicit one. This behavior matches Postgres. Release note (bug fix): Fixed a bug where the different stages of preparing, binding, and executing a prepared statement would use different implicit transactions. Now these stages all share the same implicit transaction. 76928: clusterversion,storage: revert pebblev2 table format bump r=erikgrinaker a=nicktrav Partial revert of 9ecc619. Release note: None Co-authored-by: Rafi Shamim <[email protected]> Co-authored-by: Nick Travers <[email protected]>
- Loading branch information
Showing
19 changed files
with
537 additions
and
221 deletions.
There are no files selected for viewing
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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
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
Oops, something went wrong.