From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pgbench - allow backslash-continuations in custom scripts |
Date: | 2015-06-19 19:20:24 |
Message-ID: | 55846B78.8000809@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 06/19/2015 02:51 PM, Tom Lane wrote:
> Josh Berkus <josh(at)agliodbs(dot)com> writes:
>> On 05/14/2015 12:10 PM, Fabien COELHO wrote:
>>> Add backslash continuations to pgbench custom scripts.
>
>> I don't personally agree. I believe that it it worth breaking backwards
>> compatibility to support line breaks in pgbench statements, and that if
>> we're not going to do that, supporting \ continuations is of little value.
>
> I tend to agree on that bottom line; having this be inconsistent with psql
> does not seem like a win.
>
>> I'm not clear on why we'd need a full SQL lexer.
>
> So you don't get fooled by semicolons embedded in string literals or
> comments.
I take it we ignore those now? I mean, personally, it wouldn't break
anything for me but since some other benhcmarks involve random text
generators ....
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2015-06-19 19:27:59 | Re: pretty bad n_distinct estimate, causing HashAgg OOM on TPC-H |
Previous Message | Alvaro Herrera | 2015-06-19 19:19:25 | Re: The real reason why TAP testing isn't ready for prime time |