pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michael Banck <michael.banck@credativ.de>
To: Yugo Nagata <nagata@sraoss.co.jp>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: pg_verify_checksums -d option (was: Re: pg_verify_checksums -r option)
Date: Mon, 27 Aug 2018 13:34:12 +0200
Message-ID: <20180827113411.GA22768@nighthawk.caipicrew.dd-dns.de> (raw)
In-Reply-To: <20180827195336.b54fe3d60204f38c4aa42d64@sraoss.co.jp>
References: <7d5d3f34-ec64-602a-d7af-858eb686c86d@2ndquadrant.com>
	<20180827195336.b54fe3d60204f38c4aa42d64@sraoss.co.jp>

Hi,

On Mon, Aug 27, 2018 at 07:53:36PM +0900, Yugo Nagata wrote:
> On Fri, 24 Aug 2018 18:01:09 +0200
> Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote:
> > I'm curious about this option:
> > 
> >   -r RELFILENODE         check only relation with specified relfilenode
> > 
> > but there is no facility to specify a database.
> > 
> > Also, referring to the relfilenode of a mapped relation seems a bit
> > inaccurate.
> > 
> > Maybe reframing this in terms of the file name of the file you want
> > checked would be better?
> 
> If we specified 1234 to -r option, pg_verify_shceksums checks not only 1234
> but also 1234_vm, 1234_fsm, and 1234.1, 1234.2, ... and so on, so I think
> it makes senses to allow to specify a relfilenode instead of a file name.
> 
> I think it is reasonable to add a option to specify a database, although
> I don't know which character is good because both -d and -D are already used....

Maybe the -d (debug) option should be revisited as well. Mentioning
every scanned block generates a huge amount of output which might be
useful during development but does not seem very useful for a stable
release. AFAICT there is no other debug output for now.

So it could be renamed to -v (verbose) and only mention each scanned
file, e.g. (errors/checksum mismatches are still reported of course).

Then -d could (in the future, I guess that is too late for v11) be used
for -d/--dbname (or make that only a long option, if the above does not
work).


Michael

-- 
Michael Banck
Projektleiter / Senior Berater
Tel.: +49 2166 9901-171
Fax:  +49 2166 9901-100
Email: michael.banck@credativ.de

credativ GmbH, HRB Mönchengladbach 12080
USt-ID-Nummer: DE204566209
Trompeterallee 108, 41189 Mönchengladbach
Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer

Unser Umgang mit personenbezogenen Daten unterliegt
folgenden Bestimmungen: https://www.credativ.de/datenschutz




view thread (23+ messages)  latest in thread

Message-ID: <20180827113411.GA22768@nighthawk.caipicrew.dd-dns.de>
Permalink:  ../20180827113411.GA22768@nighthawk.caipicrew.dd-dns.de/
Also on:    postgresql.org/message-id/20180827113411.GA22768@nighthawk.caipicrew.dd-dns.de

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: michael.banck@credativ.de, nagata@sraoss.co.jp, peter.eisentraut@2ndquadrant.com
  Subject: Re: pg_verify_checksums -d option (was: Re: pg_verify_checksums -r option)
  In-Reply-To: <20180827113411.GA22768@nighthawk.caipicrew.dd-dns.de>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox