Re: Unfortunate choice of short switch name in pgbench - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: Unfortunate choice of short switch name in pgbench
Date
Msg-id alpine.DEB.2.10.1402271621550.24661@sto
Whole thread Raw
In response to Re: Unfortunate choice of short switch name in pgbench  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Unfortunate choice of short switch name in pgbench  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
>>> ISTM that this is an unfortunate but unlikely mistake, as "-p" is
>>> used in all postgresql commands to signify the port number (psql,
>>> pg_dump, pg_basebackup, createdb, ...).
>
>> Plus other tools already use -P for progress, such as rsync.
>
> Yeah, but they don't make -P take an integer argument.  It's that
> little frammish that makes this problem significant.

I do not see a strong case to make options with arguments case insensitive 
as a general rule. If this is done for -p/-P, why not -t/-T?

If you really fell you must remove -P, please replace it by another 
one-letter, I use this option nearly everytime a run pgbench.

-- 
Fabien.



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: GiST support for inet datatypes
Next
From: David E. Wheeler
Date:
Subject: Re: jsonb and nested hstore