| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, 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-20 18:01:38 |
| Message-ID: | CAKFQuwY5i-iS7kWXdRVTKh=j7czqC_GKmyBgn1HuW1d2-iMq2w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sunday, March 20, 2016, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> * Allow backslash commands to span lines, probably by adopting the
> rule that backslash immediately followed by newline is to be ignored
> within a backslash command. This would not be compatible with psql,
> though, at least not unless we wanted to change psql too.
>
>
This would be appreciated. The main case I find wanting this is writing
out long \copy expressions. Solving really complex ones using temporary
tables works but being able to spread it out over multiple lines would be a
welcomed addition.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitry Dolgov | 2016-03-20 18:29:56 | Re: jsonb array-style subscription |
| Previous Message | Tom Lane | 2016-03-20 17:07:49 | Re: pgbench - allow backslash-continuations in custom scripts |