| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tatsuo Ishii <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 03:07:31 |
| Message-ID: | 30255.1541214451@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | 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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-11-03 03:56:58 | Re: backend crash on DELETE, reproducible locally |
| Previous Message | Corey Huinker | 2018-11-03 02:53:05 | Re: COPY FROM WHEN condition |