Re: pgbench -M option can be specified more than once

From: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: andres(at)anarazel(dot)de, ishii(at)sraoss(dot)co(dot)jp, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pgbench -M option can be specified more than once
Date: 2018-11-03 12:00:46
Message-ID: 20181103.210046.1700165445229024615.t-ishii@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Andres Freund <andres(at)anarazel(dot)de> writes:
>> On 2018-11-03 10:12:14 +0900, Tatsuo Ishii wrote:
>>> One of my colleagues actually believed that if both "-M extended" and
>>> "-M prepared" were specified, pgbench runs in mixture of those
>>> modes. So I felt avoiding such misunderstanding is more important.
>
>> I regularly specify options multiple times, and I'd hate for that to not
>> work anymore. It's really useful to set defaults for scripts that then
>> can be overwritten by the caller by passing on "$@" (i.e. all script
>> arguments).
>
> Yeah, there's an ancient tradition that "last switch wins" when receiving
> conflicting command-line options. I think we should tread very carefully
> in breaking that.

Yes, I think that is a fair argument. Proposal withdrawn.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2018-11-03 12:12:27 Re: partitioned indexes and tablespaces
Previous Message Thomas Munro 2018-11-03 11:03:06 Re: pread() and pwrite()