Re: [HACKERS] Index corruption with CREATE INDEX CONCURRENTLY - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: [HACKERS] Index corruption with CREATE INDEX CONCURRENTLY
Date
Msg-id CAH2-WzmuOjy+sF4x=yN1V9mLSgFF355Kw1HYNONhMcLZKt1h8g@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Index corruption with CREATE INDEX CONCURRENTLY  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Feb 17, 2017 at 9:31 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> This seems like it'd be quite a different tool than amcheck, though.
> Also, it would only find broken-HOT-chain corruption, which might be
> a rare enough issue to not deserve a single-purpose tool.

FWIW, my ambition for amcheck is that it will have checks for a large
variety of invariants that involve the heap, and related SLRU
structures such as MultiXacts. Though, that would probably necessitate
code written by other people that are subject matter experts in areas
that I am not.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: David Christensen
Date:
Subject: Re: [HACKERS] [PATCH] Add pg_disable_checksums() and supportinginfrastructure
Next
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] pg_recvlogical.c doesn't build with--disable-integer-datetimes