Re: Add progress reporting to pg_verifybackup

From: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Add progress reporting to pg_verifybackup
Date: 2023-02-06 06:33:22
Message-ID: CAD21AoAK8ic=d02+HGoatO7wiVF28W6avvuFfg2KijggvCxwUQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Feb 6, 2023 at 2:45 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Mon, Feb 06, 2023 at 12:27:51PM +0900, Masahiko Sawada wrote:
> > I thought that too, but I thought it's better to ignore it, instead of
> > erroring out. For example, we can specify both --disable and
> > --progress options to pg_checksum commands, but we don't write any
> > progress information in this case.
>
> Well, if you don't feel strongly about that, that's fine by me as
> well, so I have applied your v3 with the tweaks I posted previously,
> without the restriction on --skip-checksums.

Thank you!

Regards,

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2023-02-06 06:53:54 Re: Exit walsender before confirming remote flush in logical replication
Previous Message Tom Lane 2023-02-06 06:00:34 Re: POC PATCH: copy from ... exceptions to: (was Re: VLDB Features)