You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the plugin fails to load if Postgres is not initially available. More importantly, it never attempts to reconnect in this scenario. In automated cloud deployments or docker-compose like scenarios, this is problematic since ordering cannot be fixed. Is it possible to let the plugin load and continue reconnection attempts even if Postgres is not initially available?
The text was updated successfully, but these errors were encountered:
Currently, the plugin fails to load if Postgres is not initially available. More importantly, it never attempts to reconnect in this scenario. In automated cloud deployments or docker-compose like scenarios, this is problematic since ordering cannot be fixed. Is it possible to let the plugin load and continue reconnection attempts even if Postgres is not initially available?
The text was updated successfully, but these errors were encountered: