fix: prevent reuse of broken connections in postgres pool #7792
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.
Description of change
fixes #5112
passes the error back to the
pg-pool
release callback.there aren't tests, though - because we don't really do mocking of the database for our tests & forcing a failing database is rather difficult. until we can more gracefully do mocks / spies / etc, I'm not sure the best way to verify this functionality.
I did verify it by running a long running query,
kill -TERM
ing the postgres database & then observing the code flow.Pull-Request Checklist
master
branchnpm run lint
passes with this changenpm run test
passes with this changeFixes #0000