Re: pg_verify_checksums -d option (was: Re: pg_verify_checksums -r option)
Masahiko Sawada <sawada.mshk@gmail.com>
From: Masahiko Sawada <sawada.mshk@gmail.com>
To: Yugo Nagata <nagata@sraoss.co.jp>
Cc: Fabien COELHO <coelho@cri.ensmp.fr>,
Michael Banck <michael.banck@credativ.de>, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2018-09-04T08:16:09Z
Lists: pgsql-hackers
On Mon, Sep 3, 2018 at 10:06 PM, Yugo Nagata <nagata@sraoss.co.jp> wrote: > Hi, > > On Sat, 1 Sep 2018 07:40:40 +0200 (CEST) > Fabien COELHO <coelho@cri.ensmp.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
Commits
-
pg_verify_checksums: rename -d to --verbose
- a846e6d0239d 12.0 landed
- a840a8ac7b8a 11.0 landed