Deadlock detection and prevention in PostgreSQL

Introduction

Deadlocks happen when two or more database tasks wait for each other to finish, causing a standstill. Detecting and preventing deadlocks helps keep the database running smoothly without freezing.

When multiple users try to update the same data at the same time.

When transactions lock resources in different orders causing a cycle.

When you want to ensure your application handles database conflicts gracefully.

When you notice your database queries sometimes hang or fail unexpectedly.

When designing systems that require high concurrency and data integrity.

Syntax

PostgreSQL

-- PostgreSQL automatically detects deadlocks and aborts one transaction.
-- To prevent deadlocks, use consistent locking order and short transactions.

-- Example: Lock rows in the same order in all transactions
BEGIN;
SELECT * FROM accounts WHERE id IN (1, 2) FOR UPDATE;
-- perform updates
COMMIT;

PostgreSQL detects deadlocks automatically and aborts one of the conflicting transactions.

Prevent deadlocks by accessing tables and rows in the same order in all transactions.

Examples

This transaction locks account 1 first, then account 2, preventing deadlocks if all transactions follow this order.

PostgreSQL

BEGIN;
SELECT * FROM accounts WHERE id = 1 FOR UPDATE;
SELECT * FROM accounts WHERE id = 2 FOR UPDATE;
-- update balances
COMMIT;

This transaction locks account 2 first, then account 1, which can cause deadlocks if another transaction locks in reverse order.

PostgreSQL

BEGIN;
SELECT * FROM accounts WHERE id = 2 FOR UPDATE;
SELECT * FROM accounts WHERE id = 1 FOR UPDATE;
-- update balances
COMMIT;

This query shows current sessions waiting for locks, helping to identify deadlock situations.

PostgreSQL

-- To detect deadlocks, check PostgreSQL logs or use:
SELECT * FROM pg_stat_activity WHERE wait_event_type = 'Lock';

Sample Program

This example shows two sessions locking rows in opposite order, causing a deadlock. PostgreSQL detects it and aborts one transaction to resolve the deadlock.

PostgreSQL

-- Simulate deadlock detection
-- Session 1
BEGIN;
SELECT * FROM accounts WHERE id = 1 FOR UPDATE;

-- Session 2
BEGIN;
SELECT * FROM accounts WHERE id = 2 FOR UPDATE;

-- Session 1 tries to lock account 2
SELECT * FROM accounts WHERE id = 2 FOR UPDATE;
-- Session 2 tries to lock account 1
SELECT * FROM accounts WHERE id = 1 FOR UPDATE;

-- PostgreSQL detects deadlock and aborts one transaction automatically.

Important Notes

Keep transactions short to reduce deadlock chances.

Use consistent locking order in your application code.

Check PostgreSQL logs for deadlock details if errors occur.

Summary

Deadlocks happen when transactions wait on each other in a cycle.

PostgreSQL detects deadlocks automatically and aborts one transaction.

Prevent deadlocks by locking resources in the same order and keeping transactions short.

Practice

1. What is a deadlock in PostgreSQL?

easy

A. A performance optimization technique for faster queries.

B. A syntax error in SQL statements causing query failure.

C. A backup process that locks tables during data export.

D. A situation where two or more transactions wait indefinitely for each other to release locks.

Solution

1. Step 1: Understand transaction locking

   Transactions acquire locks on resources to maintain data integrity.

2. Step 2: Define deadlock

   A deadlock occurs when transactions wait on each other in a cycle, causing indefinite waiting.

3. Final Answer:

   A situation where two or more transactions wait indefinitely for each other to release locks. -> Option D

4. Quick Check:

   Deadlock = cyclic waiting [OK]

Hint: Deadlock means transactions wait forever on each other [OK]

Common Mistakes:

• Confusing deadlock with syntax errors
• Thinking deadlock improves performance
• Mixing deadlock with backup locking

2. Which of the following is the correct way to acquire locks to prevent deadlocks in PostgreSQL?

easy

A. Acquire locks on resources in random order.

B. Acquire locks on resources in the same order in all transactions.

C. Never acquire any locks in transactions.

D. Acquire locks only after committing the transaction.

Solution

1. Step 1: Understand lock acquisition order

   Acquiring locks in a consistent order prevents circular waiting.

2. Step 2: Identify correct practice

   All transactions should acquire locks on resources in the same order to avoid deadlocks.

3. Final Answer:

   Acquire locks on resources in the same order in all transactions. -> Option B

4. Quick Check:

   Consistent lock order = no deadlock [OK]

Hint: Always lock resources in the same order [OK]

Common Mistakes:

• Locking resources randomly
• Not locking resources at all
• Locking after commit

3. Consider two transactions in PostgreSQL:
-- Transaction 1
BEGIN;
UPDATE accounts SET balance = balance - 100 WHERE id = 1;
UPDATE accounts SET balance = balance + 50 WHERE id = 2;
-- waits here

-- Transaction 2
BEGIN;
UPDATE accounts SET balance = balance + 100 WHERE id = 2;
UPDATE accounts SET balance = balance - 50 WHERE id = 1;
-- waits here
What will PostgreSQL do when both transactions wait for each other?

medium

A. Both transactions will wait forever causing a deadlock.

B. Both transactions will succeed without any issue.

C. PostgreSQL will detect the deadlock and abort one transaction automatically.

D. PostgreSQL will merge both transactions into one.

Solution

1. Step 1: Identify deadlock scenario

   Both transactions hold locks and wait for the other's lock, creating a cycle.

2. Step 2: PostgreSQL deadlock detection

   PostgreSQL automatically detects deadlocks and aborts one transaction to break the cycle.

3. Final Answer:

   PostgreSQL will detect the deadlock and abort one transaction automatically. -> Option C

4. Quick Check:

   Deadlock detected = abort one transaction [OK]

Hint: PostgreSQL aborts one transaction on deadlock detection [OK]

Common Mistakes:

• Assuming infinite waiting without abort
• Thinking transactions merge automatically
• Believing both succeed without conflict

4. You have the following PostgreSQL code causing a deadlock:

BEGIN;
LOCK TABLE orders IN ACCESS EXCLUSIVE MODE;
UPDATE customers SET name = 'Alice' WHERE id = 1;
-- Transaction 2 starts here
BEGIN;
LOCK TABLE customers IN ACCESS EXCLUSIVE MODE;
UPDATE orders SET status = 'shipped' WHERE id = 10;

What is the main issue causing the deadlock?

medium

A. Transactions lock tables in different orders causing circular wait.

B. Using SHARE MODE lock instead of EXCLUSIVE MODE.

C. Updating different tables in the same transaction.

D. Missing COMMIT statements after updates.

Solution

1. Step 1: Analyze lock order

   Transaction 1 locks orders first, then updates customers; Transaction 2 locks customers first, then updates orders.

2. Step 2: Identify circular wait

   Each transaction waits for the other's locked table, causing deadlock due to different lock order.

3. Final Answer:

   Transactions lock tables in different orders causing circular wait. -> Option A

4. Quick Check:

   Different lock order = deadlock risk [OK]

Hint: Lock tables in same order to avoid deadlock [OK]

Common Mistakes:

• Blaming lock mode instead of order
• Thinking updating different tables causes deadlock
• Ignoring missing COMMIT as cause

5. You want to prevent deadlocks in a multi-user PostgreSQL system updating inventory and sales tables. Which strategy is best?

hard

A. Keep transactions short and acquire locks on inventory then sales in all transactions.

B. Acquire locks on sales first, then inventory, but only in some transactions.

C. Avoid using transactions to prevent locking.

D. Use long transactions to batch updates and reduce lock frequency.

Solution

1. Step 1: Understand deadlock prevention

   Keeping transactions short reduces lock time; consistent lock order prevents cycles.

2. Step 2: Apply best practice

   Always lock inventory first, then sales, in all transactions to avoid deadlocks.

3. Final Answer:

   Keep transactions short and acquire locks on inventory then sales in all transactions. -> Option A

4. Quick Check:

   Short transactions + consistent lock order = deadlock prevention [OK]

Hint: Short transactions + consistent lock order prevent deadlocks [OK]

Common Mistakes:

• Locking in inconsistent order
• Avoiding transactions entirely
• Using long transactions increasing lock time