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

From Fabien COELHO
Subject Re: [HACKERS] pgbench - allow to store select results intovariables
Date
Msg-id alpine.DEB.2.20.1701051033260.3661@lancre
Whole thread Raw
In response to Re: [HACKERS] pgbench - allow to store select results into variables  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hello Tom,

> Please look at changing \into to be a SQL-command-ending backslash
> command as we previously discussed.

Hmmm.

I do want storing results & compound command ending to be orthogonal.

In order to keep this feature, I think that I can move the 
"into/ginto/gset/..." at the end of the command. For the compound command 
list to necessarily end, I can probably do some reassembly as a post phase 
on Commands in pgbench so that the impact on the lexer is much reduced, in 
particular without undue "hackery" as you put it.

-- 
Fabien.



pgsql-hackers by date:

Previous
From: Etsuro Fujita
Date:
Subject: Re: [HACKERS] postgres_fdw : altering foreign table not invalidatingprepare statement execution plan.
Next
From: Fabien COELHO
Date:
Subject: Re: [HACKERS] proposal: session server side variables