Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make PgListener recover from UnexpectedEof #2

Merged

Conversation

rex-remind101
Copy link
Member

This is often encountered when the host the db is on is restarted. For example, a reboot of AWS Aurora causes this. If we don't handle this properly the PgListeners are stuck in an erroring state, even when the DB is back online. By catching it here, we will reconnect when it is (eventually) back online.

original pr: launchbadge#2684

This is often encountered when the host the db is on is restarted.
For example, a reboot of AWS Aurora causes this. If we don't handle this
properly the PgListeners are stuck in an erroring state, even when the DB
is back online. By catching it here, we will reconnect when it is
(eventually) back online.
@rex-remind101 rex-remind101 force-pushed the pg_listener_should_recover_from_unexpected_eof branch from 04f1ad1 to 80a3ce2 Compare September 29, 2023 19:45
@rex-remind101 rex-remind101 merged commit 5624992 into remind/main Sep 29, 2023
64 checks passed
@rex-remind101 rex-remind101 deleted the pg_listener_should_recover_from_unexpected_eof branch October 20, 2023 22:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants