Re: Progress reporting for pg_verify_checksums

Fabien COELHO <coelho@cri.ensmp.fr>

From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Michael Banck <michael.banck@credativ.de>
Cc: Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>, michael@paquier.xyz, alvherre@2ndquadrant.com, mailings@oopsware.de, thomas.munro@enterprisedb.com, pgsql-hackers@postgresql.org
Date: 2019-03-18T22:14:01Z
Lists: pgsql-hackers
> I have rebased it now.

Thanks. Will look at it.

>> If the all of aboves are involved, the line would look as the
>> follows.
>>
>> [=======================             ] ( 63% of 12.53 GB, 179 MB/s, ETC 26s)
>>
>> # Note that this is just an opinion.
>>
>> (pg_checksum runs fast at the beginning so ETC behaves somewhat
>> strange in the meanwhile.)
>
> I haven't changed that for now as it seems to be a bit more involved.
> I'd like to hear other opinions on whether that is worthwhile?

I think that the bar is overkill, but ETC is easy and nice.

>>> +     /* we handle SIGUSR1 only, and toggle the value of show_progress */
>>> +     if (signum == SIGUSR1)
>>> +             show_progress = !show_progress;
>>
>> SIGUSR1 *toggles* progress.
>
> Not sure what you mean here,

Probably it is meant to simplify the comment?

-- 
Fabien.

Commits

  1. Add progress reporting to pg_checksums

  2. Fix thinko when bumping on temporary directories in pg_verify_checksums

  3. Fix thinko when bumping on temporary directories in pg_checksums