From ebe124eacd7c3faa36ed358e7cc1d7c5b419e5f6 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 4 May 2024 14:18:09 +0200 Subject: Merging upstream version 15.6. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/explicit-locking.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/src/sgml/html/explicit-locking.html') diff --git a/doc/src/sgml/html/explicit-locking.html b/doc/src/sgml/html/explicit-locking.html index 9a28c47..728395b 100644 --- a/doc/src/sgml/html/explicit-locking.html +++ b/doc/src/sgml/html/explicit-locking.html @@ -1,5 +1,5 @@ -13.3. Explicit Locking
13.3. Explicit Locking
Prev UpChapter 13. Concurrency ControlHome Next

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.3. Explicit Locking

13.3. Explicit Locking
Prev UpChapter 13. Concurrency ControlHome Next

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

PostgreSQL provides various lock modes to control concurrent access to data in tables. These modes can be used for application-controlled locking in situations where @@ -393,4 +393,4 @@ SELECT pg_advisory_lock(q.id) FROM

The functions provided to manipulate advisory locks are described in Section 9.27.10. -

Prev Up Next
13.2. Transaction Isolation Home 13.4. Data Consistency Checks at the Application Level
\ No newline at end of file +

Prev Up Next
13.2. Transaction Isolation Home 13.4. Data Consistency Checks at the Application Level
\ No newline at end of file -- cgit v1.2.3