This repository has been archived by the owner on Mar 16, 2022. It is now read-only.
Allow more exception types to trigger retries and bans #87
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.
There was a bug in psycopg2 prior to 2.9 that misclassified some connection failures. This prevented us from retrying in those cases. Rather than play whack-a-mole, let's just expand the notion of retryable exception to the PEP249
Error
base class (basically, any kind of database-related error).