intermediateLocking, MVCC & Deadlocks

Why doesn't a long-running SELECT block a concurrent UPDATE under PostgreSQL's MVCC?

They operate on different row versions — the reader sees a consistent snapshot from when it started, while the writer creates a new version, with no shared lock to contend over.

Ready to master this question?

Generate a complete walkthrough — background, the full answer in plain language, a working code example explained line by line, a real-world scenario, common mistakes, and how this same question gets asked in different ways.

Next Step

Continue to What's the actual root cause of most production deadlocks, and what's the real fix (not just a mitigation)? →← Back to all Transaction Mastery questions