Re: new heapcheck contrib module - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: new heapcheck contrib module
Date
Msg-id CAH2-Wzmh101MsYxavHdLtXLyT=ecWdNH2-YOvVce598=zzjQCg@mail.gmail.com
Whole thread Raw
In response to Re: new heapcheck contrib module  (Mark Dilger <mark.dilger@enterprisedb.com>)
Responses Re: new heapcheck contrib module  (Mark Dilger <mark.dilger@enterprisedb.com>)
List pgsql-hackers
I mean an interface that's friendly to DBAs, that verifies an entire database. No custom sql query required. Something that provides a reasonable mix of verification options based on high level directives. All verification methods can be combined in a granular, possibly randomized fashion. Maybe we can make this run in parallel. 

For example, maybe your heap checker code sometimes does index probes for a subset of indexes and heap tuples. It's not hard to combine it with the rootdescend stuff from amcheck. It should be composable. 

The interface you've chosen is a good starting point. But let's not miss an opportunity to make everything work together. 

Peter Geoghegan
(Sent from my phone)

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: relocating the server's backup manifest code
Next
From: Mark Dilger
Date:
Subject: Re: new heapcheck contrib module