From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: new heapcheck contrib module |
Date: | 2020-04-20 19:37:07 |
Message-ID: | CAH2-Wzmh101MsYxavHdLtXLyT=ecWdNH2-YOvVce598=zzjQCg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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)
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Dilger | 2020-04-20 19:40:28 | Re: new heapcheck contrib module |
Previous Message | Robert Haas | 2020-04-20 18:54:41 | Re: relocating the server's backup manifest code |