PostgreSQL Performance & Query Optimization · Lezione

Comprendere lock e deadlock

Apprenda i diversi tipi di lock in PostgreSQL e come identificare e prevenire i deadlock.

Comprendere lock e deadlock è una lezione PostgreSQL Performance & Query Optimization gratuita su CoddyKit. Questa è la lezione 1 di 4. Puoi leggere la lezione completa qui gratuitamente — poi esercitati direttamente nel browser con un editor di codice integrato e un tutor IA disponibile 24/7. Fa parte del percorso di apprendimento PostgreSQL Performance & Query Optimization, e i tuoi progressi si sincronizzano tra il web e l'app CoddyKit. Il corso PostgreSQL Performance & Query Optimization include 4 lezioni in totale.

Parti di questa lezione non sono ancora state tradotte e vengono mostrate in inglese.

Welcome to Concurrency

When many users or applications access a database at the same time, it's called concurrency. PostgreSQL, like other databases, needs to manage these concurrent operations carefully.

Without proper management, multiple operations could try to modify the same data simultaneously, leading to inconsistencies or errors. This is where locks come in!

What are Database Locks?

A database lock is a mechanism that controls access to data by multiple transactions. It ensures that data remains consistent and prevents conflicts.

Data Integrity: Guarantees that data is accurate and reliable.
Consistency: Ensures that transactions see a consistent view of the database.
Conflict Prevention: Stops different operations from corrupting data by trying to write to the same place at the same time.

PostgreSQL Lock Modes

PostgreSQL uses various lock modes to define the level of access transactions have to a particular resource. These modes determine compatibility: some allow shared access, while others are exclusive.

ACCESS SHARE: Acquired by simple SELECT statements. Allows other transactions to also acquire ACCESS SHARE, ROW SHARE, etc.
ROW EXCLUSIVE: Acquired by INSERT, UPDATE, DELETE. Allows concurrent reads but prevents other transactions from acquiring ROW EXCLUSIVE on the same row.
ACCESS EXCLUSIVE: The most restrictive lock. Acquired by DROP TABLE or TRUNCATE. Prevents all other access to the table.

Implicit Locks in Action

Most of the time, PostgreSQL automatically acquires the necessary locks for you. These are called implicit locks.

For example:

When you run a SELECT query, an ACCESS SHARE lock is acquired on the table.
When you run an UPDATE, INSERT, or DELETE query, a ROW EXCLUSIVE lock is acquired on the affected rows and a corresponding table-level lock.

This automatic locking ensures data consistency without you needing to explicitly manage it.

Explicit Table Locks

While implicit locks handle most cases, you can also acquire locks explicitly using the LOCK TABLE command. This is useful for specific scenarios where you need to control access more precisely.

You can specify the lock mode, like ACCESS EXCLUSIVE to block all other operations, or SHARE for concurrent index creation.

Demo: Locking a Table

Try running this example. It creates a simple table and then explicitly locks it in ACCESS EXCLUSIVE mode. While this lock is held (for the duration of the transaction), no other transaction can read or write to this table.

CREATE TABLE IF NOT EXISTS inventory (
    item_id SERIAL PRIMARY KEY,
    item_name VARCHAR(100),
    quantity INT
);
TRUNCATE TABLE inventory;
INSERT INTO inventory (item_name, quantity) VALUES ('Widget A', 50);

-- This command acquires an ACCESS EXCLUSIVE lock on the 'inventory' table.
-- In a real scenario, this would block other operations until committed.
LOCK TABLE inventory IN ACCESS EXCLUSIVE MODE;

SELECT 'Table locked successfully!' AS status;

-- The lock is released when this script finishes (transaction commits).

Explicit Row Locks: SELECT FOR UPDATE

For fine-grained control, you can lock specific rows using SELECT FOR UPDATE or SELECT FOR SHARE. This is crucial for preventing race conditions in application logic.

SELECT ... FOR UPDATE: Acquires a ROW EXCLUSIVE lock on selected rows. Other transactions can read but cannot update or lock these rows for update until your transaction commits.
SELECT ... FOR SHARE: Acquires a ROW SHARE lock. Other transactions can also acquire ROW SHARE locks, but not ROW EXCLUSIVE.

Spotting Active Locks with pg_locks

To see what locks are currently active in your database, you can query the pg_locks system view. This view provides detailed information about each lock.

Key columns to look for:

pid: The process ID holding or waiting for the lock.
locktype: Type of resource being locked (e.g., relation, transactionid).
mode: The lock mode (e.g., ACCESS SHARE, ROW EXCLUSIVE).
granted: t if the lock is held, f if waiting.

You can query it like this:

SELECT * FROM pg_locks WHERE NOT granted;

Understanding Deadlocks

A deadlock occurs when two or more transactions are waiting for each other to release a resource, resulting in a standstill. Neither transaction can proceed.

PostgreSQL automatically detects deadlocks and aborts one of the transactions (the 'deadlock victim') to allow the other to complete. This usually results in an error message for the aborted transaction.

A Classic Deadlock Scenario

Imagine two transactions, T1 and T2, trying to update two rows, Row A and Row B:

T1: Locks Row A, then tries to lock Row B.
T2: Locks Row B, then tries to lock Row A.

At this point, T1 holds A and waits for B, while T2 holds B and waits for A. Neither can progress. PostgreSQL detects this cycle and terminates one transaction.

Lock Mode Check

Which lock mode is typically acquired by a simple SELECT statement?

Recap: Locks & Deadlocks

We've covered the essentials of database locks and deadlocks in PostgreSQL. Locks ensure data consistency and integrity in concurrent environments, operating through various lock modes.

Remember:

PostgreSQL uses implicit and explicit locks.
pg_locks helps monitor active locks.
Deadlocks occur when transactions wait for each other, and PostgreSQL detects and resolves them by aborting one transaction.

Understanding these concepts is key to building robust and performant applications!

Domande Frequenti

La lezione «Comprendere lock e deadlock» è gratuita?

Sì — il testo completo di «Comprendere lock e deadlock» è gratuito qui sul web. Per esercitarvi in modo interattivo (un editor di codice integrato e un tutor IA 24/7) e sbloccare il resto del corso PostgreSQL Performance & Query Optimization, passa a CoddyKit PRO. Il corso PostgreSQL Performance & Query Optimization include 4 lezioni in totale.

Cosa imparerò in «Comprendere lock e deadlock»?

Apprenda i diversi tipi di lock in PostgreSQL e come identificare e prevenire i deadlock. Eserciti PostgreSQL Performance & Query Optimization con codice pratico che esegui direttamente nel browser, e un tutor IA 24/7 risponde alle tue domande mentre lavori sulla lezione.

Ho bisogno di esperienza per iniziare PostgreSQL Performance & Query Optimization?

Non è richiesta alcuna esperienza precedente. PostgreSQL Performance & Query Optimization su CoddyKit è strutturato per principianti e studenti avanzati, quindi puoi iniziare da qui o dall'inizio e procedere al tuo ritmo. Questa è la lezione 1 di 4.

Quanto tempo richiede la lezione «Comprendere lock e deadlock»?

La maggior parte delle lezioni CoddyKit richiede circa 5–10 minuti. Ogni lezione è breve e interattiva, quindi fai progressi costanti e riprendi esattamente da dove hai lasciato su web e app.

Posso scrivere ed eseguire codice in questa lezione PostgreSQL Performance & Query Optimization?

Sì. Ogni lezione PostgreSQL Performance & Query Optimization include un editor di codice integrato, quindi scrivi ed esegui codice reale direttamente nel tuo browser e ricevi feedback istantaneo dall'IA — nessuna configurazione locale necessaria.

Tutte le lezioni di questo corso

Comprendere lock e deadlock
Identificare e risolvere la contesa sui lock
Strategie di locking a livello di riga
Advisory lock per coordinare le applicazioni

← Torna a PostgreSQL Performance & Query Optimization