only report wait times from clients currently waiting to match behavior of pgbouncer #655
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 maxwait reported by pgcat differs in how it's measured from pgbouncer
maxwait in pgbouncer
Pgcat instead tracked the longest wait time ever encountered by a client.
If a client in pgcat waited for a few seconds during a slow period, it would continue to report a high maxwait until it disconnects, even all of its subsequent queries have low wait times.
This changes pgcat behavior to match pgbouncer; max wait reported is now the max over all clients currently waiting.
https://discord.com/channels/1013868243036930099/1015389720622153819/1181065797892853771