| From: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| 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:40:28 |
| Message-ID: | 6F3E35CB-C81E-49FF-A6E9-8E23FCA86FF6@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Apr 20, 2020, at 12:37 PM, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
>
> 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.
Ok, I'll work in that direction and repost when I have something along those lines.
Thanks again for your input.
—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2020-04-20 19:42:10 | Re: new heapcheck contrib module |
| Previous Message | Peter Geoghegan | 2020-04-20 19:37:07 | Re: new heapcheck contrib module |