From 2a0f262beff32ba86bcb58f3273214e5d0517c09 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Tue, 14 May 2024 21:16:24 +0200 Subject: Merging upstream version 16.3. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/locking-indexes.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/src/sgml/html/locking-indexes.html') diff --git a/doc/src/sgml/html/locking-indexes.html b/doc/src/sgml/html/locking-indexes.html index d8d56b6..1158810 100644 --- a/doc/src/sgml/html/locking-indexes.html +++ b/doc/src/sgml/html/locking-indexes.html @@ -1,5 +1,5 @@ -13.7. Locking and Indexes
13.7. Locking and Indexes
Prev UpChapter 13. Concurrency ControlHome Next

13.7. Locking and Indexes #

+13.7. Locking and Indexes

13.7. Locking and Indexes
Prev UpChapter 13. Concurrency ControlHome Next

13.7. Locking and Indexes #

Though PostgreSQL provides nonblocking read/write access to table data, nonblocking read/write access is not currently offered for every @@ -39,4 +39,4 @@ applications that need to index scalar data. When dealing with non-scalar data, B-trees are not useful, and GiST, SP-GiST or GIN indexes should be used instead. -

Prev Up Next
13.6. Caveats Home Chapter 14. Performance Tips
\ No newline at end of file +

Prev Up Next
13.6. Caveats Home Chapter 14. Performance Tips
\ No newline at end of file -- cgit v1.2.3