Repository navigation
[P2] Recover PostgreSQL connectivity after a disconnect #53
Description
Recorded during review of main at a1eb305ccfa2f3fc8ddede4875765cf1b099bd2b. This issue records a finding only; no implementation changes were made or requested.
Finding
The application holds a single PostgreSQL client. When its connection task exits, it logs the error but does not reconnect or replace the client. Connection and credential operations then remain unavailable until the application restarts.
Evidence
Desired outcome
Use connection management with recovery and readiness reporting. Test loss and restoration of database connectivity without restarting the application.
Activity
michielbdejong commentedon Sep 16, 2026
Fixed in #73 —
Securitynow holds its PostgreSQL client behind a background supervisor that reconnects with exponential backoff and swaps the shared client in automatically on recovery. AddedSecurity::is_ready()and a/healthzendpoint. Covered by a test that kills the backend viapg_terminate_backendand confirms the connection self-heals without a restart.Generated by Claude Code