Why might you prefer transaction-level advisory locks over session-level advisory locks in PostgreSQL?

hard📝 Conceptual Q10 of 15

PostgreSQL - Transactions and Concurrency

ATransaction-level locks can be held across multiple transactions

BSession-level locks are faster and more efficient

CTransaction-level locks automatically release at transaction end, preventing stale locks

DSession-level locks do not block other sessions

Step-by-Step Solution

Solution:

Step 1: Compare session-level and transaction-level advisory locks
Session-level locks persist until the session ends, risking stale locks if the session crashes or forgets to release.
Step 2: Understand benefits of transaction-level locks
Transaction-level locks automatically release when the transaction ends, avoiding stale locks and simplifying lock management.
Final Answer:
Transaction-level locks automatically release at transaction end, preventing stale locks -> Option C
Quick Check:
Auto-release locks = transaction-level advantage [OK]

Quick Trick: Transaction-level locks auto-release, avoiding stale locks [OK]

Common Mistakes:

Master "Transactions and Concurrency" in PostgreSQL

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free