| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Michael Paquier <michael(at)paquier(dot)xyz>, Stephen Frost <sfrost(at)snowman(dot)net>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] pgbench - allow to store select results into variables |
| Date: | 2019-01-10 19:00:33 |
| Message-ID: | 201901101900.mv7zduch6sad@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-Jan-10, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> > Now let's see how the buildfarm likes this ...
>
> This \cset thing seem like an incredibly badly thought out kluge.
> What is its excuse to live?
The reason is that you can set variables from several queries in one
network trip.
We can take it out I guess, but my impression was that we already pretty
much had a consensus that it was wanted.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-01-10 19:14:25 | Re: [HACKERS] pgbench - allow to store select results into variables |
| Previous Message | Dave Page | 2019-01-10 18:23:47 | Re: Policy on cross-posting to multiple lists |