Re: pgbench - allow to store select results into variables

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgbench - allow to store select results into variables
Date: 2016-07-13 20:13:43
Message-ID: 32591.1468440823@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Wed, Jul 13, 2016 at 3:02 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I note also that we were talking a couple months ago
>> about trying to align psql and pgbench backslash commands more closely.
>> This would not be a good step in that direction.

> True, but I'd still argue that \into is a lot more readable than
> \gset. Maybe both programs should support both commands.

Meh, personal preference there no doubt. I'd be okay with both programs
supporting both commands, but the \into command as described here would
be quite unreasonable to implement in psql. It needs to act more like
a semicolon-substitute, as \g and the rest of its family do. (I think
I'd also lobby for spelling it \ginto.)

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2016-07-13 20:16:25 Re: pgbench - allow to store select results into variables
Previous Message Robert Haas 2016-07-13 20:11:27 Re: sslmode=require fallback