Re: [HACKERS] pgbench - allow to store select results into variables - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [HACKERS] pgbench - allow to store select results into variables
Date
Msg-id 20181116214307.uhpir3nvwuvjftxa@alvherre.pgsql
Whole thread Raw
In response to Re: [HACKERS] pgbench - allow to store select results intovariables  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses Re: [HACKERS] pgbench - allow to store select results into variables  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: [HACKERS] pgbench - allow to store select results intovariables  (Fabien COELHO <coelho@cri.ensmp.fr>)
List pgsql-hackers
On 2017-Nov-04, Fabien COELHO wrote:

> Think of one initialization followed by two appends:
> 
>   SELECT 1 AS x \cset
>   SELECT 2 \; SELECT 3 AS y \cset
>   SELECT 4 \; SELECT 5 \; SELECT 6 AS z \gset
> 
> In the end, we must have the full 6 queries
> 
>   "SELECT 1 AS x \; SELECT 2 \; SELECT 3 AS y \; SELECT 4 \; SELECT 5 \; SELECT 6 AS z"
> 
> and know that we want to set variables from queries 1, 3 and 6 and ignore
> the 3 others.

I'm not sure I understand this.  Why is the "SELECT 2" ignored?  (I can
see why the 4 and 5 are ignored: they are not processed by gset).

What exactly does \cset do?  I thought "SELECT 2 \; SELECT 3 AS y \cset"
would search for the \; and process *both* queries.

I think the doc addition should be split.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Early WIP/PoC for inlining CTEs
Next
From: Thomas Munro
Date:
Subject: Re: Refactoring the checkpointer's fsync request queue