Cookbook recipe

Set sane statement, lock, and idle timeouts

Applies to PostgreSQL 13–17 Last reviewed May 2026 Grounded in source
Estimated investigation4 min

Scenario

Without timeouts, one bad query or held lock can hang the whole system. A few defaults protect you. Diagnose it Check current values: SHOW statement_timeout; SHOW lock_timeout; SHOW idle_in_transaction_session_timeout; Why it happens Defaults are 0 (disabled).…

Investigation Path

Without timeouts, one bad query or held lock can hang the whole system. A few defaults protect you.

Diagnose it

Check current values:

SHOW statement_timeout;
SHOW lock_timeout;
SHOW idle_in_transaction_session_timeout;

Why it happens

Defaults are 0 (disabled). That means a runaway query, a lock waiter, or a leaked transaction can run forever, starving everyone else.

This is a Pro lesson

Get every Learning Pathway and cookbook recipe — grounded in PostgreSQL source code, with diagnostics, fixes, and prevention for each topic.

Continue this lesson to learn:

  • How to fix it
  • Prevent it next time
  • Related & next steps
  • All 36 Learning Pathway lessons
  • 170+ cookbook recipes
  • Source-grounded diagnostics & fixes

Secure checkout Cancel anytime Source-grounded

Career Impact

This scenario builds production judgment and operational confidence under pressure.

Open Career Dashboard →

Keep going

Related & next steps

Was this helpful?

← All cookbook recipes