Re: Add progress reporting to pg_verifybackup - Mailing list pgsql-hackers

From Masahiko Sawada
Subject Re: Add progress reporting to pg_verifybackup
Date
Msg-id CAD21AoD=+pmo4u3UryhTnWV+Pf8MDkWyVx6t6LMzPQUijXFZFQ@mail.gmail.com
Whole thread Raw
In response to Re: Add progress reporting to pg_verifybackup  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Add progress reporting to pg_verifybackup
List pgsql-hackers
On Thu, Feb 2, 2023 at 3:12 PM Michael Paquier <michael@paquier.xyz> wrote:
>
> On Thu, Feb 02, 2023 at 02:57:44PM +0900, Masahiko Sawada wrote:
> > 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.
>
> What about command_checks_all()?  It should check for stderr, stdout
> as well as the expected error code.

Seems a good idea. Please find an attached patch.

Regards,

--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com

Attachment

pgsql-hackers by date:

Previous
From: Önder Kalacı
Date:
Subject: Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher
Next
From: shveta malik
Date:
Subject: Re: [PATCH] Reuse Workers and Replication Slots during Logical Replication