feat: set default pgbouncer.maxClientConnections
to 1000
#543
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.
What issues does your PR fix?
What does your PR do?
pgbouncer.maxClientConnections
from100
to1000
1000
is well beyond what should be required in most deployments, so this should prevent users from running into a confusing situation where the connection limit is exceeded, and random things start failing (with the only error logs being in the PGBouncer deployment)Checklist
For all Pull Requests
For releasing ONLY