Postgres Lock Incident Triage

What you get

Upload pg_stat_activity and optional pg_locks CSV snapshots. Receive:

• incident tier and snapshot-freshness warning
• blocker-to-waiter chain table
• long query, long transaction, and idle-in-transaction ranking
• protected-backend warnings for autovacuum, replication, and backups
• first 15-minute non-destructive action plan
• cancel-versus-terminate decision table
• recovery verification checklist
• internal status update and post-incident follow-up

Example input

• pg_stat_activity CSV including pg_blocking_pids(pid)
• optional pg_locks CSV
• impact, primary/replica role, and snapshot timestamp

Example output preview

• SEV-2: PID 814 blocks five sessions.
• Reconfirm PID 814, owner, query, backend start, and transaction purpose.
• Pause the producing job before adding more waiters.
• Prefer owner coordination and reviewed cancellation.
• Require human approval before termination and verify rollback load afterward.

Delivery and boundaries

The package never connects to Postgres or executes SQL. Never take action against a PID from a stale snapshot. Human approval is required before session termination.

Part of the Postgres Release-Safety Family

• Free Postgres Migration Risk Checker - GREEN/AMBER/RED preflight before merge
• Postgres Migration Review: Locks + Rollback Plan - full PASS/REVISE/BLOCK release artifact
• Postgres EXPLAIN Reviewer - plan bottlenecks, index candidates, rewrites