node-postgres (pg)

Playbooks for node-postgres (pg)

1. Diagnosing node-postgres connection timeouts at startup

   Covers distinguishing pool exhaustion from a genuine reachability/auth failure, which node-postgres reports identically, and the immediate config-side responses to each. Does not cover a pool that starts healthy and exhausts gradually under sustained traffic from a code-level leak — that's the missing-release playbook, a different root cause with the same visible error.

   Unverifiedno reproductions yetWhy this confidence?

2. Finding and fixing a node-postgres connection leak

   Covers the specific signature of a client-side leak — pool usage climbing steadily under sustained normal traffic rather than in a burst — and the try/finally fix. Does not cover a pool that's simply undersized for a legitimate concurrent burst at startup; that's the connect-timeout playbook, a different pattern in the same counters.

   Unverifiedno reproductions yetWhy this confidence?

Versions

• 8