From: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com> |
---|---|
To: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pgbench -M option can be specified more than once |
Date: | 2018-11-03 01:26:13 |
Message-ID: | CAMsGm5cUrLDdsLJiJME9rPiADcueVAVnpuQyXVBharoTH6iCjA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
In many cases, it is handy to be able to specify an option in an alias, but
still be able to override on the actual command line.
I can't say whether that is useful with this specific option, but it seems
the same debate could be had about almost any option. I'm pretty sure the
existing behaviour is consistent with other options, with the exception of
a few (e.g. pg_dump --table), which are explicitly documented as being
cumulative.
On Fri, 2 Nov 2018 at 21:12, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> wrote:
> > Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> writes:
> >> While playing with pgbench, I found multiple "-M query_mode" can be
> >> set more than once. For example,
> >
> > I think that's true of just about every option in all of our programs.
> > Why is this one instance so much worse than others that it deserves
> > to be handled differently?
>
> 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.
>
> Best regards,
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese:http://www.sraoss.co.jp
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2018-11-03 01:28:40 | Re: pgbench -M option can be specified more than once |
Previous Message | Tatsuo Ishii | 2018-11-03 01:12:14 | Re: pgbench -M option can be specified more than once |