> On May 14, 2020, at 1:02 PM, Peter Eisentraut
> <peter.eisentr...@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. 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?
The tool doesn't hold a single snapshot or transaction for the lifetime of
checking the entire database. A future improvement to the tool might add
parallelism. Users could do all of this in scripts, but having a single tool
with the most commonly useful options avoids duplication of effort.
—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
