Re: Progress reporting for pg_verify_checksums
Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
From: Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
To: coelho@cri.ensmp.fr
Cc: michael.banck@credativ.de, michael@paquier.xyz, alvherre@2ndquadrant.com,
mailings@oopsware.de, thomas.munro@enterprisedb.com,
pgsql-hackers@postgresql.org
Date: 2019-03-19T00:04:14Z
Lists: pgsql-hackers
Hello. At Mon, 18 Mar 2019 23:14:01 +0100 (CET), Fabien COELHO <coelho@cri.ensmp.fr> wrote in <alpine.DEB.2.21.1903182311130.23282@lancre> > > > 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. I'm fine with that. > >>> + /* 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? Sorry. I meant that "it can be turned off and a perhaps-garbage line is left alone after turning off. Don't we need to erase it?". regards. -- Kyotaro Horiguchi NTT Open Source Software Center
Commits
-
Add progress reporting to pg_checksums
- 280e5f14056b 12.0 landed
-
Fix thinko when bumping on temporary directories in pg_verify_checksums
- da453004869d 11.3 landed
-
Fix thinko when bumping on temporary directories in pg_checksums
- 6eebfdc38b17 12.0 landed