Re: Unfortunate choice of short switch name in pgbench

From: KONDO Mitsumasa <kondo(dot)mitsumasa(at)lab(dot)ntt(dot)co(dot)jp>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
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-28 07:47:51
Message-ID: 53103F27.7070701@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

(2014/02/28 2:39), Tom Lane wrote:
> Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> writes:
>>> 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?
I'll say the same thing. And if we remove -P short option in pgbench, it means
that -P with integer will be forbided in postgres command. Surely, we don't hope so.

>> If you really fell you must remove -P, please replace it by another
>> one-letter, I use this option nearly everytime a run pgbench.
>
> Meh. If I thought -P would be that popular, I'd expect people to get
> used to the issue. I don't believe it though.
At least, a user which is interested in postgres performance tuning(include
kernel options, etc) will often use this option. I recommended this feature,
because we can see the bottle-neck which we have not seen:) I believe you will
also become to like it more and more, while you use it.

Regards,
--
Mitsumasa KONDO
NTT Open Source Software Center

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2014-02-28 07:54:47 Re: jsonb and nested hstore
Previous Message Christophe Pettus 2014-02-28 07:36:07 Re: jsonb and nested hstore