Postgres: Do not attempt to deallocate a statement if the connection is no longer active. #3258
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
…is no longer active.
tenderlove
added a commit
that referenced
this pull request
Oct 20, 2011
Postgres: Do not attempt to deallocate a statement if the connection is no longer active.
tenderlove
added a commit
that referenced
this pull request
Oct 20, 2011
Postgres: Do not attempt to deallocate a statement if the connection is no longer active.
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.
The PostgreSQL adapter attempts to clear out the statement cache on
reconnect!, which in turn issues aDEALLOCATEquery for each cached statement. If the connection has been lost, the query results in anPGErrorbeing raised.This change first checks the connection is OK before attempting to
DEALLOCATEthe statement.Fixes issue #3160