On Fri, May 17, 2024 at 4:10 PM Mark Dilger <mark.dil...@enterprisedb.com> wrote: > 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.
I understood that. I was just pointing out that an index that looks even somewhat like that is already quite unnatural. -- Peter Geoghegan
