Re: Corrupted btree index on HEAD because of covering indexes - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Corrupted btree index on HEAD because of covering indexes
Date
Msg-id CAH2-WzkJU7cqa-M-XAgPU7Wk-nV=moYr=L4qkO4fjx-t20fZVQ@mail.gmail.com
Whole thread Raw
In response to Re: Corrupted btree index on HEAD because of covering indexes  (Teodor Sigaev <teodor@sigaev.ru>)
Responses Re: Corrupted btree index on HEAD because of covering indexes
List pgsql-hackers
On Wed, Apr 25, 2018 at 8:06 AM, Teodor Sigaev <teodor@sigaev.ru> wrote:
> Leave it in both places. In ideal world, in amcheck test we need to create a
> broken index, but I don't know a correct way to do it :)

There are many ways to create a broken index, but they're hard to make
work with pg_regress. :-)

It looks like you pushed v1, which didn't have the tests and other
changes you asked for. Attached patch adds those back.

Thanks
-- 
Peter Geoghegan

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: perltidy version
Next
From: Alvaro Herrera
Date:
Subject: Re: perltidy version