Re: pg_verify_checksums -d option (was: Re: pg_verify_checksums -r option)

From: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
To: Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>
Cc: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Michael Banck <michael(dot)banck(at)credativ(dot)de>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_verify_checksums -d option (was: Re: pg_verify_checksums -r option)
Date: 2018-09-04 08:16:09
Message-ID: CAD21AoAJGp6ZAC32=p0sv55jFgnMFT8spdu=uWgRmg6ecpOj8A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Sep 3, 2018 at 10:06 PM, Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp> wrote:
> Hi,
>
> On Sat, 1 Sep 2018 07:40:40 +0200 (CEST)
> Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> wrote:
>
>> > Attached is a patch to allow pg_verity_checksums to specify a database
>> > to scan. This is usefule for users who want to verify checksums of relations
>> > in a specific database. We can specify a database by OID using -d or --dboid option.
>> > Also, when -g or --global-only is used only shared relations are scaned.
>>
>> It seems that the patch does not apply anymore. Could you rebase it?
>
> I attached the rebased patch.

FWIW, I think it would be good if we can specify multiple database
oids to the -d option, like "pg_verify_checksums -d 12345 -d 23456".
Maybe it's the same for the -r option.

Regards,

--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2018-09-04 08:26:12 Re: Make executor's Range Table an array instead of a List
Previous Message David Rowley 2018-09-04 08:14:29 Re: Make executor's Range Table an array instead of a List