Re: Unfortunate choice of short switch name in pgbench

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Unfortunate choice of short switch name in pgbench
Date: 2014-02-27 17:33:26
Message-ID: alpine.DEB.2.10.1402271621550.24661@sto
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2014-02-27 17:37:46 Re: jsonb and nested hstore
Previous Message Tom Lane 2014-02-27 17:30:57 Re: GiST support for inet datatypes