Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index.

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