Chapter 13. Concurrency Control

Supported versions: Current (18) / 17 / 16 / 15 / 14

Development versions: 19 / 20devel

Unsupported versions: 13 / 12 / 11 / 10 / 9.6 / 9.5 / 9.4 / 9.3 / 9.2 / 9.1 / 9.0 / 8.4 / 8.3 / 8.2 / 8.1 / 8.0 / 7.4 / 7.3 / 7.2 / 7.1

Development snapshot. PostgreSQL 20devel has not been released. Content may change.

Chapter 13. Concurrency Control
Prev	Up	Part II. The SQL Language	Home	Next

Table of Contents

13.1. Introduction

13.2. Transaction Isolation

13.2.1. Read Committed Isolation Level
13.2.2. Repeatable Read Isolation Level
13.2.3. Serializable Isolation Level

13.3. Explicit Locking

13.3.1. Table-Level Locks
13.3.2. Row-Level Locks
13.3.3. Page-Level Locks
13.3.4. Deadlocks
13.3.5. Advisory Locks

13.4. Data Consistency Checks at the Application Level

13.4.1. Enforcing Consistency with Serializable Transactions
13.4.2. Enforcing Consistency with Explicit Blocking Locks

13.5. Serialization Failure Handling

13.6. Caveats

13.7. Locking and Indexes

This chapter describes the behavior of the PostgreSQL database system when two or more sessions try to access the same data at the same time. The goals in that situation are to allow efficient access for all sessions while maintaining strict data integrity. Every developer of database applications should be familiar with the topics covered in this chapter.

Prev	Up	Next
12.11. Limitations	Home	13.1. Introduction

Report a documentation issue

Read the upstream documentation. For corrections, first check the current manual.