introduce PGBOUNCER_CONNECT_QUERY parameter to configure connect_query setting #95
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
added 4 commits
January 29, 2018 15:20
…y setting this is super useful for setting things like statement_timeout on backend connection initiation.
nixme
added a commit
to FatbearLabs/heroku-buildpack-pgbouncer
that referenced
this pull request
Jan 27, 2024
nixme
added a commit
to FatbearLabs/heroku-buildpack-pgbouncer
that referenced
this pull request
Jan 27, 2024
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.
TLDR: this is super useful for setting things like statement_timeout on backend connection initiation.
Backstory:
We are running pgbouncer in statement pooling mode. We were setting
statement_timeouton connection start in activerecord, to make sure we don't have lingering long-running queries. But for some reason we had a really bad query almost take down the database, so we started to investigate.Long story short: As soon as pgbouncer re-creates its connections (by default at least once every hour), they do not have
statement_timeout(and other session-level props) set.This patch allows defining a query to execute after pgbouncer creates a new backend connection.