Re: pgbench - allow backslash-continuations in custom scripts - Mailing list pgsql-hackers

From David Steele
Subject Re: pgbench - allow backslash-continuations in custom scripts
Date
Msg-id 56E6ADE5.2090100@pgmasters.net
Whole thread Raw
In response to Re: pgbench - allow backslash-continuations in custom scripts  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
Responses Re: pgbench - allow backslash-continuations in custom scripts  (Fabien COELHO <coelho@cri.ensmp.fr>)
List pgsql-hackers
On 2/18/16 6:54 AM, Kyotaro HORIGUCHI wrote:

> First, I rebased the previous patch set and merged three of
> them. Now they are of three patches.
>
>
> 1. Making SQL parser part of psqlscan independent from psql.
>
>     Moved psql's baskslsh command stuff out of original psqlscan.l
>     and some psql stuff the parser directly looked are used via a
>     set of callback functions, which can be all NULL for usages
>     from other than psql.
>
> 2. Making pgbench to use the new psqlscan parser.
>
> 3. Changing the way to hold SQL/META commands from array to
>      linked list.
>
>      The #2 introduced linked list to store SQL multistatement but
>      immediately the caller moves the elements into an array. This
>      patch totally changes the way to linked list.

Any takers to review this updated patch?

-- 
-David
david@pgmasters.net



pgsql-hackers by date:

Previous
From: David Steele
Date:
Subject: Re: Batch update of indexes
Next
From: Tomas Vondra
Date:
Subject: Re: Re: PATCH: Split stats file per database WAS: autovacuum stress-testing our system