| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgbench - allow backslash-continuations in custom scripts |
| Date: | 2016-03-21 19:50:48 |
| Message-ID: | 30529.1458589848@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> Mmph. I just don't see any benefit in being able to start a command
> in the middle of a line.
I agree that there's no functional benefit; it's a matter of consistency.
In particular, psql has always allowed you to write multiple SQL commands
per line:
SELECT 2+2; SELECT x FROM tab; SELECT y FROM othertab;
and as of yesterday pgbench supports that as well. So allowing multiple
backslash commands on a line improves consistency both with psql and with
pgbench's own behavior, IMV.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-03-21 19:55:03 | Re: Declarative partitioning |
| Previous Message | Robert Haas | 2016-03-21 19:45:22 | Re: pgbench - allow backslash-continuations in custom scripts |