Disable prepared statements when run from CLI #104
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
Apparently, when run through a connection pooler, the prepared statements from one run may persist to the next run because the underlying connection is not closed and it retains the prepared statements. This would cause the next run to fail because the prepared statement names are deterministic and would conflict with the already existing prepared statements. #100
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.
Apparently, when run through a connection pooler, the prepared statements from one run may persist to the next run because the underlying connection is not closed and it retains the prepared statements. This would cause the next run to fail because the prepared statement names are deterministic and would conflict with the already existing prepared statements.
#100