From e75d99818dd3940be997520e64db8c9e3b207e39 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Tue, 21 May 2024 07:05:26 +0200 Subject: Merging upstream version 15.7. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/index-unique-checks.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/src/sgml/html/index-unique-checks.html') diff --git a/doc/src/sgml/html/index-unique-checks.html b/doc/src/sgml/html/index-unique-checks.html index 07a62e1..52f0bdf 100644 --- a/doc/src/sgml/html/index-unique-checks.html +++ b/doc/src/sgml/html/index-unique-checks.html @@ -1,5 +1,5 @@ -64.5. Index Uniqueness Checks
64.5. Index Uniqueness Checks
Prev UpChapter 64. Index Access Method Interface DefinitionHome Next

64.5. Index Uniqueness Checks

+64.5. Index Uniqueness Checks

64.5. Index Uniqueness Checks
Prev UpChapter 64. Index Access Method Interface DefinitionHome Next

64.5. Index Uniqueness Checks

PostgreSQL enforces SQL uniqueness constraints using unique indexes, which are indexes that disallow multiple entries with identical keys. An access method that supports this @@ -106,4 +106,4 @@ target row is found in the recheck verifies that we are scanning for the same tuple values as were used in the original insertion.

-

Prev Up Next
64.4. Index Locking Considerations Home 64.6. Index Cost Estimation Functions
\ No newline at end of file +

Prev Up Next
64.4. Index Locking Considerations Home 64.6. Index Cost Estimation Functions
\ No newline at end of file -- cgit v1.2.3