Re: Progress reporting for pg_verify_checksums

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
Cc: Michael Banck <michael(dot)banck(at)credativ(dot)de>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Bernd Helmle <mailings(at)oopsware(dot)de>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Progress reporting for pg_verify_checksums
Date: 2019-03-13 07:25:15
Message-ID: 20190313072515.GB2988@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 13, 2019 at 07:22:28AM +0100, Fabien COELHO wrote:
> Does not apply because of the renaming committed by Michaël.
>
> Could you rebase?

This stuff touches pg_checksums.c, so you may want to wait one day or
two to avoid extra work... I think that I'll be able to finish the
addition of the --enable and --disable switches by then.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2019-03-13 07:26:54 Re: Offline enabling/disabling of data checksums
Previous Message Michael Paquier 2019-03-13 07:22:00 Re: Adding a TAP test checking data consistency on standby with minRecoveryPoint