Re: Progress reporting for pg_verify_checksums
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Michael Banck <michael.banck@credativ.de>
Cc: Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>, coelho@cri.ensmp.fr, alvherre@2ndquadrant.com, mailings@oopsware.de, thomas.munro@enterprisedb.com, pgsql-hackers@postgresql.org
Date: 2019-03-23T01:49:34Z
Lists: pgsql-hackers
On Fri, Mar 22, 2019 at 02:23:17PM +0100, Michael Banck wrote: > The current version prints a newline when it progress reporting is > toggled off. Do you mean there is a hazard that this happens right when > we are printing the progress, so end up with a partly garbage line? I > don't think that'd be so bad to warrant further code complexitiy, after > all, the user explicitly wanted the progress to stop. > > But maybe I am misunderstanding? The latest patch does not apply because of mainly ed308d7. Could you send a rebase? FWIW, I would remove the signal toggling stuff from the patch and keep the logic simple at this stage. Not having a solution which works on Windows is perhaps not a strong reason to not include it, but it's a sign that we could perhaps design something better, and that's annoying. Personally I think that I would just use --progress all the time and not use the signaling part at all, my 2c. -- Michael
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