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

From Peter Eisentraut
Subject Re: new heapcheck contrib module
Date
Msg-id 9317e6a4-4be9-de73-a2b5-4c9fda936aaf@2ndquadrant.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
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?

I suppose you could make an argument for a command-line wrapper around 
almost every admin-focused contrib module (pageinspect, pg_prewarm, 
pgstattuple, ...), but that doesn't seem very sensible.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Our naming of wait events is a disaster.
Next
From: Robert Haas
Date:
Subject: Re: Our naming of wait events is a disaster.