PostgreSQL

Lock wait times exceed acceptable thresholds

warning
performanceUpdated Jan 25, 2026
Technologies:
How to detect:

Queries waiting more than 1 second to acquire locks indicate contention bottlenecks that degrade user-facing performance

Recommended action:

Enable lock wait logging with log_lock_waits = on and deadlock_timeout = '1s'. Monitor PostgreSQL logs for entries showing 'process X still waiting for ShareLock on transaction Y after 1000.123 ms'. Use the blocked queries diagnostic query to identify blocking transactions.