Re: Allowing line-continuation in pgbench custom scripts - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Allowing line-continuation in pgbench custom scripts
Date
Msg-id CAHGQGwGfywr87qU5FdwdO_9wRBZacNUgpg+F5w1tTWhMuutd8w@mail.gmail.com
Whole thread Raw
In response to Allowing line-continuation in pgbench custom scripts  (Amit Langote <amitlangote09@gmail.com>)
Responses Re: Allowing line-continuation in pgbench custom scripts
List pgsql-hackers
On Mon, May 26, 2014 at 6:50 PM, Amit Langote <amitlangote09@gmail.com> wrote:
> Hi,
>
> 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
>
> For example,
>
> BEGIN;
> \setrandom  1 16500000
> UPDATE table \
>     SET col2 = (clock_timestamp() + '10s'::interval * random() * 1000), \
>         col3 = (clock_timestamp() + '10s'::interval * sin(random() *
> (2*pi()) )  * 1000) \
>     WHERE col1 = :id;
> COMMIT;
>
> instead of:
>
> BEGIN;
> \setrandom id 1 16500000
> UPDATE table SET col2 = (clock_timestamp() + '10s'::interval *
> random() * :id),  col3 = (clock_timestamp() + '10s'::interval *
> sin(random() * (2*pi()) )  * 100000) WHERE col1 = :id;
> COMMIT;
>
> Thoughts?

IMO it's better if we can write SQL in multiples line *without* a tailing
escape character, like psql's input file.

Regards,

-- 
Fujii Masao



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Re: popen and pclose redefinitions causing many warning in Windows build
Next
From: Fujii Masao
Date:
Subject: Re: Priority table or Cache table