feat: Allow infinite reconnect retries with -1 setting #574
+1
−1
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.
What kind of change does this PR introduce?
This PR introduces a feature that enables Supavisor to allow infinite reconnect retries when @reconnect_retries is set to -1.
What is the current behavior?
Currently, the reconnect logic has a hard limit. Once the number of retries exceeds @reconnect_retries, Supavisor stops attempting to reconnect if the database is unavailable.
What is the new behavior?
With this change, if @reconnect_retries is set to -1, Supavisor will never stop retrying to connect to the database.
Additional context
This supports environments that use dynamic scaling or “scale to zero” strategies where the database may be intentionally down but needs to be brought online seamlessly when connections are attempted again.
Makes “infinite” reconnection behavior a conscious user choice, helping in scenarios where the DB is scaled down and then scaled back up based on metrics.