On Wed, Feb 1, 2023 at 10:25 AM Michael Paquier <mich...@paquier.xyz> wrote:
>
> On Fri, Jan 06, 2023 at 04:28:42PM +0900, Masahiko Sawada wrote:
> > I've attached the simple patch to add the progress reporting option to
> > pg_verifybackup. The progress information is displayed with --progress
> > option only during the checksum verification, which is the most time
> > consuming task. It cannot be used together with --quiet option.
>
> That looks helpful, particularly when a backup has many relation
> files. Calculating the total size when browsing the file list looks
> fine.
>
> + /* Complain if the specified arguments conflict */
> + if (show_progress && quiet)
> + pg_fatal("cannot specify both --progress and --quiet");
>
> Nothing on HEAD proposes --progress and --quiet at the same time from
> what I can see, so just disabling the combination is fine by me. For
> the error message, I would recommend to switch to a more generic
> pattern, as of:
> "cannot specify both %s and %s", "-P/--progress", "-q/--quiet"Agreed. > > Could you add a check based on command_fails_like() in 004_options.pl, > at least? Agreed, done in v2 patch. > A second test to check after the output of --progress would > be a nice bonus, for example by sticking --progress into one of the > existing commands doing a command_like(). It seems that the --progress option doesn't work with command_like() since the progress information is written in stderr but command_like() doesn't want it. Regards, -- Masahiko Sawada Amazon Web Services: https://aws.amazon.com
v2-0001-Add-progress-reporting-to-pg_verifybackup.patch
Description: Binary data
