| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: new heapcheck contrib module |
| Date: | 2020-05-14 20:02:49 |
| Message-ID: | 9317e6a4-4be9-de73-a2b5-4c9fda936aaf@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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. Internally it 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 tables and 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2020-05-14 20:03:37 | Re: Our naming of wait events is a disaster. |
| Previous Message | Tom Lane | 2020-05-14 19:58:53 | Re: Our naming of wait events is a disaster. |