Add query_db_wait_timeout configuration option #594
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.
Hello PgBouncer team. I'd like feedback on a new configuration field. This adds a parameter (
query_db_wait_timeout
) to address the problem described in in #585.Setting
query_db_wait_timeout
to a nonzero value will disconnect a client if the following two things are true:Note that this does not require the pool to have been in a fast failure state for
query_db_wait_timeout
seconds, just that the client has been waiting and the pool is currently in a broken state when the bookkeeping occurs.Thanks in advance.