MVCC mental model in PostgreSQL - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does MVCC handle concurrent reads and writes?

In PostgreSQL's MVCC system, what happens when one transaction reads a row that another transaction is currently updating but not yet committed?

A The reading transaction sees the old committed version of the row, ignoring the uncommitted changes.

B The reading transaction sees the uncommitted changes immediately.

C The reading transaction gets an error because the row is locked.

D The reading transaction waits until the writing transaction commits or rolls back before reading the row.

💡 Hint

Think about how MVCC provides a consistent snapshot for readers.

MVCC allows readers to see the last committed version of data, so they do not block or get blocked by writers. Uncommitted changes are invisible to other transactions.

❓ query_result

intermediate

Result of concurrent transactions with MVCC

Consider two transactions in PostgreSQL:

-- Transaction 1
BEGIN;
UPDATE accounts SET balance = balance - 100 WHERE id = 1;
-- Transaction 2
BEGIN;
SELECT balance FROM accounts WHERE id = 1;

What balance does Transaction 2 see if Transaction 1 has not committed yet?

A The balance after subtracting 100 (uncommitted update).

B An error due to concurrent update.

C NULL because the row is locked.

D The balance before subtracting 100 (last committed value).

💡 Hint

Remember MVCC shows a consistent snapshot to readers.

Transaction 2 sees the last committed balance because Transaction 1's update is not committed yet.

📝 Syntax

advanced

Identify the MVCC-related error in this transaction

Which option shows a transaction that will cause a serialization failure error due to MVCC in PostgreSQL?

-- Transaction 1
BEGIN;
SELECT balance FROM accounts WHERE id = 1;
UPDATE accounts SET balance = balance + 50 WHERE id = 1;
COMMIT;

A Two concurrent transactions both read and update the same row without locking, causing serialization failure.

B A transaction that updates different rows, so no serialization failure occurs.

C A transaction that only reads data without updates, so no serialization failure occurs.

D A transaction that uses explicit locks to prevent serialization failure.

💡 Hint

Think about what causes serialization failures in MVCC.

When two transactions read and update the same row concurrently without proper locking, PostgreSQL may raise a serialization failure to maintain consistency.

❓ optimization

advanced

Optimizing MVCC vacuuming in PostgreSQL

Which approach best helps reduce bloat caused by MVCC dead tuples in PostgreSQL?

A Disabling autovacuum and manually running VACUUM FULL weekly.

B Increasing autovacuum frequency and tuning vacuum cost parameters.

C Using only DELETE statements without UPDATEs to avoid dead tuples.

D Increasing transaction isolation level to SERIALIZABLE.

💡 Hint

Think about how PostgreSQL cleans up old row versions.

Autovacuum automatically removes dead tuples created by MVCC. Increasing its frequency and tuning cost parameters helps keep tables lean.

🔧 Debug

expert

Diagnosing phantom reads under MVCC

In PostgreSQL, a transaction running at REPEATABLE READ isolation sees phantom rows after another transaction inserts new rows and commits. Why does this happen?

A Phantom reads occur because the first transaction did not commit before the second started.

B MVCC blocks all phantom reads by locking all rows in the table.

C REPEATABLE READ in PostgreSQL does not prevent phantom reads; only SERIALIZABLE does.

D Phantom reads are impossible in PostgreSQL due to MVCC.

💡 Hint

Consider the difference between REPEATABLE READ and SERIALIZABLE isolation levels.

PostgreSQL's REPEATABLE READ prevents non-repeatable reads but allows phantom reads. Only SERIALIZABLE isolation prevents phantoms by stricter locking and serialization.

Practice

1. What does MVCC in PostgreSQL primarily allow multiple users to do?

easy

A. Delete data instantly without backups

B. Run only one transaction at a time

C. Work with data simultaneously without waiting for locks

D. Automatically create database indexes

Solution

1. Step 1: Understand MVCC purpose

   MVCC stands for Multi-Version Concurrency Control, which allows multiple users to access data concurrently.

2. Step 2: Identify MVCC effect in PostgreSQL

   It lets users work without waiting for locks by providing each transaction a snapshot of data.

3. Final Answer:

   Work with data simultaneously without waiting for locks -> Option C

4. Quick Check:

   MVCC = concurrent access without waiting [OK]

Hint: MVCC means no waiting for others' data changes [OK]

Common Mistakes:

• Thinking MVCC locks data exclusively
• Believing MVCC deletes old data immediately
• Assuming only one transaction runs at a time

2. Which SQL statement correctly starts a transaction in PostgreSQL to use MVCC?

easy

A. BEGIN;

B. START;

C. BEGINNING TRANSACTION;

D. OPEN TRANSACTION;

Solution

1. Step 1: Recall PostgreSQL transaction syntax

   PostgreSQL uses BEGIN; to start a transaction.

2. Step 2: Compare options

   Only A is valid syntax. B and C use incorrect keywords, D is invalid.

3. Final Answer:

   BEGIN; -> Option A

4. Quick Check:

   PostgreSQL transaction start = BEGIN; [OK]

Hint: Use BEGIN; to start transactions in PostgreSQL [OK]

Common Mistakes:

• Using START; which is invalid syntax
• Typing OPEN TRANSACTION; which is invalid
• Confusing transaction start with commit or rollback

3. Consider this sequence in PostgreSQL:
BEGIN;
SELECT * FROM products WHERE id = 1;
UPDATE products SET price = 20 WHERE id = 1;
COMMIT;
What does the SELECT see if another transaction updated the same row before this transaction started?

medium

A. An error due to concurrent update

B. The new price updated by the other transaction

C. No rows returned because of the update

D. The old price before the other transaction's update

Solution

1. Step 1: Understand snapshot isolation in MVCC

   The SELECT sees data as it was at transaction start, ignoring later committed changes.

2. Step 2: Apply to given scenario

   Since another transaction updated before this one started, the snapshot at start excludes that committed update, so SELECT sees the old price.

3. Final Answer:

   The old price before the other transaction's update -> Option D

4. Quick Check:

   MVCC snapshot = data at tx start [OK]

Hint: SELECT sees snapshot at transaction start, not later changes [OK]

Common Mistakes:

• Expecting an error due to concurrent update
• Thinking SELECT sees the old price before the other transaction's update
• Thinking no rows returned because of the update

4. You run this code:
BEGIN;
UPDATE accounts SET balance = balance - 100 WHERE id = 1;
SELECT balance FROM accounts WHERE id = 1;
ROLLBACK;
Why might the SELECT show the updated balance even though the transaction is not committed?

medium

A. Because the transaction sees its own changes inside the transaction

B. Because ROLLBACK commits the changes automatically

C. Because SELECT ignores transaction boundaries

D. Because balance is cached outside the database

Solution

1. Step 1: Understand visibility of changes inside a transaction

   Within a transaction, you see your own uncommitted changes.

2. Step 2: Explain why SELECT shows updated balance

   Even before commit, SELECT sees the updated balance because it's in the same transaction.

3. Final Answer:

   Because the transaction sees its own changes inside the transaction -> Option A

4. Quick Check:

   Transaction sees own changes before commit [OK]

Hint: Inside transaction, you see your own updates [OK]

Common Mistakes:

• Thinking ROLLBACK commits changes
• Believing SELECT ignores transaction state
• Assuming external cache affects SELECT results

5. In PostgreSQL, if two transactions try to update the same row simultaneously, what happens to maintain MVCC consistency?

hard

A. Both transactions update the row and overwrite each other

B. One transaction waits or fails due to a lock conflict

C. PostgreSQL merges both updates automatically

D. The second transaction reads old data but commits anyway

Solution

1. Step 1: Understand MVCC row update behavior

   PostgreSQL uses row-level locks to prevent conflicting updates.

2. Step 2: Explain conflict resolution

   When two transactions update the same row, one waits or fails to keep data consistent.

3. Final Answer:

   One transaction waits or fails due to a lock conflict -> Option B

4. Quick Check:

   Concurrent updates cause lock wait or failure [OK]

Hint: Concurrent updates cause lock wait or error [OK]

Common Mistakes:

• Assuming updates merge automatically
• Believing both updates overwrite without conflict
• Thinking second transaction commits ignoring locks