Is your feature request related to a problem? Please describe.
I use pgscv with the static configuration service:, there are times when the connections to `postgres' are cut off:
{"level":"warn","service":"pgscv","time":"2026-07-03T20:13:22Z","message":"monitoring@172.17.0.1:21470/monitoring: failed to connect to `host=172.17.0.1 user=monitoring database=monitoring`: dial error (dial tcp 172.17.0.1:21470: connect: connection refused) skip"}
The problem is that there is no connection verification mechanism, which means you have to manually restart.
Describe the solution you'd like
Add a verification mechanism for services that have lost their connection. Add a global/local interval parameter for checks. For example, every 10 seconds
Describe alternatives you've considered
Temporarily made a cronjob that restarts pgscv every day
Additional context
I tried playing with parameters like skip_conn_error_mode, but maybe I don't know something.
Is your feature request related to a problem? Please describe.
I use pgscv with the static configuration
service:, there are times when the connections to `postgres' are cut off:The problem is that there is no connection verification mechanism, which means you have to manually restart.
Describe the solution you'd like
Add a verification mechanism for services that have lost their connection. Add a global/local interval parameter for checks. For example, every 10 seconds
Describe alternatives you've considered
Temporarily made a cronjob that restarts pgscv every day
Additional context
I tried playing with parameters like
skip_conn_error_mode, but maybe I don't know something.