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

From Mark Dilger
Subject Re: new heapcheck contrib module
Date
Msg-id A5662EEC-9300-4EAE-9C76-1A7E829550F7@enterprisedb.com
Whole thread Raw
In response to Re: new heapcheck contrib module  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers

> On May 14, 2020, at 1:02 PM, Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote:
>
> On 2020-05-11 19:21, Mark Dilger wrote:
>> 1) A new module, pg_amcheck, which includes a command line client for checking a database or subset of a database.
Internallyit functions by querying the database for a list of tables which are appropriate given the command line
switches,and then calls amcheck's functions to validate each table and/or index.  The options for selecting/excluding
tablesand schemas is patterned on pg_dump, on the assumption that interface is already familiar to users. 
>
> Why is this useful over just using the extension's functions via psql?

The tool doesn't hold a single snapshot or transaction for the lifetime of checking the entire database.  A future
improvementto the tool might add parallelism.  Users could do all of this in scripts, but having a single tool with the
mostcommonly useful options avoids duplication of effort. 

—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company






pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: PG 13 release notes, first draft
Next
From: Jeff Janes
Date:
Subject: Re: SEQUENCE values (duplicated) in some corner cases when crash happens