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

[Mark Dilger]

> On May 17, 2024, at 1:00 PM, Peter Geoghegan <p...@bowt.ie> wrote:
> 
> Many different parts of the B-Tree code will fight against allowing
> duplicates of the same value to span multiple leaf pages -- this is
> especially true for unique indexes. 

The quick-and-dirty TAP test I wrote this morning is intended to introduce 
duplicates across page boundaries, not to test for ones that got there by 
normal database activity.  In other words, the TAP test forcibly corrupts the 
index by changing a value on one side of a boundary to be equal to the value on 
the other side of the boundary.  Prior to the corrupting action the values were 
all unique.

—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company