Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index. - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index.
Date
Msg-id CAH2-Wz=GW68721KanMzbBippDGAJ_YyO8Z49-0nfBW0ZzS1Gdg@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index.  (Mark Dilger <mark.dilger@enterprisedb.com>)
List pgsql-hackers
On Fri, May 17, 2024 at 4:10 PM Mark Dilger
<mark.dilger@enterprisedb.com> wrote:
> The quick-and-dirty TAP test I wrote this morning is intended to introduce duplicates across page boundaries, not to
testfor ones that got there by normal database activity.  In other words, the TAP test forcibly corrupts the index by
changinga value on one side of a boundary to be equal to the value on the other side of the boundary.  Prior to the
corruptingaction the values were all unique. 

I understood that. I was just pointing out that an index that looks
even somewhat like that is already quite unnatural.

--
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Mark Dilger
Date:
Subject: Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index.
Next
From: Robert Haas
Date:
Subject: Re: Speed up clean meson builds by ~25%