Fix PostgreSQL unusable connection after query failure #1148
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
mvorisek
force-pushed
the
fix_pgsql_unusable_after_failed_statement
branch
from
558e1fb to
b1aaf59
Compare
mvorisek
force-pushed
the
fix_pgsql_unusable_after_failed_statement
branch
2 times, most recently
from
5031a0d to
3e39733
Compare
mvorisek
force-pushed
the
fix_pgsql_unusable_after_failed_statement
branch
from
3e39733 to
f1ae0ff
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.
the solution is to savepoint every non-select query