Re: Progress reporting for pg_verify_checksums - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Progress reporting for pg_verify_checksums
Date
Msg-id 20180903142132.oo3pekbn7sph7igz@alvherre.pgsql
Whole thread Raw
In response to Re: Progress reporting for pg_verify_checksums  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses Re: Progress reporting for pg_verify_checksums  (Michael Banck <michael.banck@credativ.de>)
Re: Progress reporting for pg_verify_checksums  (Thomas Munro <thomas.munro@enterprisedb.com>)
List pgsql-hackers
On 2018-Sep-01, Fabien COELHO wrote:

> > If -P was forgotten and pg_verify_checksums operates on a large cluster,
> > the caller can send SIGUSR1 to pg_verify_checksums to turn progress
> > status reporting on during runtime.
> 
> Hmmm. I cannot say I like the signal feature much. Would it make sense for
> the progress to be on by default, and to have a quiet option instead?

Hmm, I recall this technique being used elsewhere and is sometimes
useful.  Can't remember where though -- by manpages, it's not rsync nor
pv ...

How about making it a toggle?  Default off, enable-able by option,
toggleable by signal.  (If you enable it via the signal, what's the rate
to report at?)

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: TR: pgadmin not displaying data from postgresql_fdw
Next
From: Michael Banck
Date:
Subject: Re: Progress reporting for pg_verify_checksums