On Wed, Jul 13, 2016 at 4:02 PM, Tom Lane <t...@sss.pgh.pa.us> wrote:
> Robert Haas <robertmh...@gmail.com> writes: > > On Sat, Jul 9, 2016 at 7:52 AM, Fabien COELHO <coe...@cri.ensmp.fr> > wrote: > >> If someone thinks that "gset" is a good idea for pgbench, which I > don't, it > >> could be implemented. I think that an "into" feature, like PL/pgSQL & > ECPG, > >> makes more sense for scripting. > > > I agree: I like \into. > > > But: > > >> SELECT 1, 2 \; SELECT 3; > >> \into one two three > > > I think that's pretty weird. > > Yeah, that's seriously nasty action-at-a-distance in my view. I'd be okay > with > > SELECT 1, 2 \into one two > SELECT 3 \into three > > but I do not think that a metacommand on a following line should > retroactively affect the execution of a prior command, much less commands > before the last one. You need a test and a definition for: SELECT 1, 2; SELECT 3; \into x, y, z It should fail - "too many variables" - right? David J.