From: | Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp> |
---|---|
To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
Cc: | 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-03 13:06:18 |
Message-ID: | 20180903220618.5da91f48300ba6498db73620@sraoss.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
Regards,
--
Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>
Attachment | Content-Type | Size |
---|---|---|
0001-Allow-pg_verify_checksums-to-specify-a-database-v2.patch | text/x-diff | 4.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-09-03 13:51:40 | Re: pg_verify_checksums failure with hash indexes |
Previous Message | Chapman Flack | 2018-09-03 12:28:07 | Re: Stored procedures and out parameters |