Use PostgreSQL protocol for deallocating prepared statements #1797
Conversation
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 method uses the PostgreSQL protocol Close method to deallocate a prepared statement. This means that it can succeed in an aborted transaction.
This uses the PostgreSQL protocol to deallocate a prepared statement instead of a SQL statement. This allows it to work even in an aborted transaction.
This was referenced Nov 11, 2023
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 allows Deallocate to succeed even inside of an aborted transaction.
It also only removes the connection's record of a prepared statement if the deallocation succeeds.
This should resolve the issue identified in #1795 and may also resolve #1791.