Add PGBOUNCER_SERVER_RESET_QUERY_ALWAYS config #129
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
|
? |
beanieboi
approved these changes
Jun 12, 2020
|
@pimeys thx! could you please rebase the Changelog.md |
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 gives us a possibility to clear prepared statements in a transaction mode.
If the application respectfully runs all queries in transactions; it allows us to use prepared statements in this mode. The downside of this is more roundtrips to the database even for simple reads through
BEGINandCOMMIT/ROLLBACK, but it allows us to utilize the escaping and SQL injection protections of PostgreSQL.This is the missing part for Prisma2 to work with Heroku's Pgbouncer offering with slight modifications to the runtime to force transactions in every query, if detecting Pgbouncer.