Re: Why does pg_checksums -r not have a long option? - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Why does pg_checksums -r not have a long option?
Date
Msg-id 20190528025648.GA1348@paquier.xyz
Whole thread Raw
In response to Re: Why does pg_checksums -r not have a long option?  (Michael Banck <michael.banck@credativ.de>)
Responses Re: Why does pg_checksums -r not have a long option?  (Fabien COELHO <coelho@cri.ensmp.fr>)
Re: Why does pg_checksums -r not have a long option?  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On Mon, May 27, 2019 at 10:17:43AM +0200, Michael Banck wrote:
> Before we switch to -f out of consistency with oid2name, we should
> consider Magnus' argument from
> CABUevEzoeXaxbcYmMZsNF1aqdCwovys7-ChqCuGRY5+nsQZFew@mail.gmail.com IMO:
>
> |I have no problem with changing it to -r. -f seems a bit wrong to me,
> |as it might read as a file. And in the future we might want to implement
> |the ability to take full filename (with path), in which case it would
> |make sense to use -f for that.

You could also use a long option for that without a one-letter option,
like --file-path or such, so reserving a one-letter option for a
future, hypothetical use is not really a stopper in my opinion.  In
consequence, I think that that it is fine to just use -f/--filenode.
Any objections or better suggestions from other folks here?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Gurjeet Singh
Date:
Subject: Fix comment in pgcrypto tests
Next
From: Amit Langote
Date:
Subject: Re: BEFORE UPDATE trigger on postgres_fdw table not work