Hey team,
Just wanted to share my feedback on operational issue we saw yesterday/today.
We use direct connection by our API services and dedicated pooler to connect from clickhouse.
Yesterday we started to see these in logs:
<img width="1450" height="184" alt="image" src="https://github.com/user-attachments/assets/179bcccc-4ab7-48f1-9478-b25bebf853ba" />It took some time to figure out, because direct connection worked fine, but some requests would fail. Finally we decided to bite the bullet and restart the project. Pooler got revived. The danger was that if we didn't notice - some features would have been dead for days...
We would appreciate some logic that restarts pgBouncer automatically if it dies silently.
Kind regards, Vlad
Vlad Zotov reported an issue where the dedicated pooler (pgBouncer) stopped working silently, causing some requests to fail. The problem was resolved by restarting the project, but Vlad suggests implementing a mechanism to automatically restart pgBouncer if it fails silently.