fix: add auto_reconnect to the Postgrex.Notifications #24
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.
If Postgres is not available at the time of startup,
Postgrex.Notifications.start_link
will kill the strategy process each time the supervisor restarts it, until all retries are exhausted.libcluster_postgres/lib/strategy.ex
Line 60 in 82e36ab
This PR fixes this behavior by starting
Postgrex.Notifications
with the:auto_reconnect
option. This prevents the process from killing and allows it to keep retrying connection attempts in the background. Once Postgres becomes available again, the process will cast the node name into the cluster.