Re: pgbench - allow backslash-continuations in custom scripts

From: David Steele <david(at)pgmasters(dot)net>
To: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, robertmhaas(at)gmail(dot)com
Cc: coelho(at)cri(dot)ensmp(dot)fr, michael(dot)paquier(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pgbench - allow backslash-continuations in custom scripts
Date: 2016-03-14 12:26:13
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: 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?


In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2016-03-14 12:33:08 Re: Re: PATCH: Split stats file per database WAS: autovacuum stress-testing our system
Previous Message David Steele 2016-03-14 12:09:29 Re: Batch update of indexes