fix(connections): clearer message for PgBouncer 'no pool configured' - #84
Merged
Conversation
Connecting through a PgBouncer that has no pool registered for the database/user returns 'FATAL: No pool configured for database: ...'. That's a server-side pooler config issue, not a Nembrix problem — map it to a short, clear message instead of the raw FATAL. Unit-tested.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
A user connecting through PgBouncer hit:
That's a server-side pooler config issue (the DB/user isn't registered in PgBouncer's pool list), not a Nembrix bug. Map it in
short_connect_errorto a clear one-liner:Added to the existing connect-error shortener + a unit-test case.
cargo check/clippyclean.