Skip to content

Deadlock

In one line

A deadlock is when two transactions wait for each other's locks — neither can proceed, one must be rolled back.

In simple words

A deadlock happens when:

  1. Transaction A locks resource X, then tries to lock resource Y
  2. Transaction B locks resource Y, then tries to lock resource X
  3. A waits for B to release Y, B waits for A to release X
  4. Neither can proceed — deadlock!

The database detects deadlocks and resolves them by aborting one transaction (the "victim") with a deadlock error. The application must retry the aborted transaction.

Prevention strategies:

  1. Consistent lock ordering — always lock resources in the same order
  2. Short transactions — reduce the window for deadlocks
  3. Lower isolation — fewer locks = fewer deadlock opportunities
  4. Lock timeouts — give up waiting after a period

Deadlocks are normal in concurrent systems — handle them with retry logic.

Example

sql
-- Deadlock scenario:
-- Transaction A:
BEGIN;
UPDATE accounts SET balance = balance - 100 WHERE id = 1; -- locks account 1
UPDATE accounts SET balance = balance + 100 WHERE id = 2; -- waits for account 2 lock

-- Transaction B (concurrent):
BEGIN;
UPDATE accounts SET balance = balance - 50 WHERE id = 2; -- locks account 2
UPDATE accounts SET balance = balance + 50 WHERE id = 1; -- waits for account 1 lock
-- DEADLOCK! A has 1, wants 2. B has 2, wants 1.

-- Fix: always lock in the same order
-- Transaction B (fixed):
BEGIN;
UPDATE accounts SET balance = balance + 50 WHERE id = 1; -- lock 1 first
UPDATE accounts SET balance = balance - 50 WHERE id = 2; -- then lock 2

Deadlock: A locks 1→wants 2, B locks 2→wants 1. Fix: always lock in the same order (1 then 2) to prevent circular dependencies.

Common confusions

  • Confused with: race condition

    The difference: A race condition is about incorrect results from concurrent execution order. A deadlock is about transactions being stuck waiting for each other forever. Race conditions produce wrong answers; deadlocks produce no answer (transactions hang). Deadlocks are detected and resolved; race conditions are subtle bugs.

Related terms

Related Resources

Related Lessons

Decode error messages

Plain-English explanations of common errors — what they mean, why they happen, and how to fix them.

View errors

← Back to glossary