| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | Michael Banck <michael(dot)banck(at)credativ(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Progress reporting for pg_verify_checksums |
| Date: | 2018-09-03 14:21:32 |
| Message-ID: | 20180903142132.oo3pekbn7sph7igz@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Banck | 2018-09-03 14:34:20 | Re: Progress reporting for pg_verify_checksums |
| Previous Message | Alvaro Herrera | 2018-09-03 14:06:17 | Re: TR: pgadmin not displaying data from postgresql_fdw |