A Postgres client experienced connection failures after 90 minutes of inactivity due to a Cisco router's idle timeout setting. The router dropped the connection after 60 minutes of no data transmission as its default configuration. Adjusting the tcp_keepalives_idle setting in Postgres to send keep alive messages before the router's idle timeout can prevent such disconnections. The post emphasizes the need for understanding backend and database interactions for effective troubleshooting.
Sort: