| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Amit Langote <amitlangote09(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Allowing line-continuation in pgbench custom scripts |
| Date: | 2014-05-26 17:50:03 |
| Message-ID: | CAMkU=1wLSMBDY0YoxZH+weMS3Mjm6d1YphPoFi4jjAo10k0Yig@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Monday, May 26, 2014, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Amit Langote <amitlangote09(at)gmail(dot)com <javascript:;>> writes:
> > In a custom pgbench script, it seems convenient to be able to split a
> > really long query to span multiple lines using an escape character
> > (bash-style). Attached adds that capability to read_line_from_file()
> > in pgbench.c
>
> This seems pretty likely to break existing scripts that happen to contain
> backslashes. Is it really worth the compatibility risk?
>
Do you mean due to the bugs you point out, or in general? Is it really at
all likely that someone has ended a line of their custom benchmark file
with a backslash? I'm having a hard time seeing what, other than malice,
would prod someone to do that.
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matteo Beccati | 2014-05-26 17:51:25 | Re: [PATCH] Replacement for OSSP-UUID for Linux and BSD |
| Previous Message | Andres Freund | 2014-05-26 17:31:31 | Re: [PATCH] Replacement for OSSP-UUID for Linux and BSD |