From: | "Andres Freund" <andres(at)anarazel(dot)de> |
---|---|
To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: PATCH: Batch/pipelining support for libpq |
Date: | 2020-11-18 23:17:36 |
Message-ID: | 6528520e-e5b1-4814-9877-aa6852aaa5f8@www.fastmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi
On Wed, Nov 18, 2020, at 09:51, Alvaro Herrera wrote:
> On 2020-Nov-14, Daniel Verite wrote:
>
> > The patch I posted in [1] was pretty simple, but at the time, query
> > results were always discarded. Now that pgbench can instantiate
> > variables from query results, a script can do:
> > select 1 as var \gset
> > select :var;
> > This kind of sequence wouldn't work in batch mode since it
> > sends queries before getting results of previous queries.
> >
> > So maybe \gset should be rejected when inside a batch section.
>
> Hah.
>
> Hacking pgbench extensively is beyond what I'm willing to do for this
> feature at this time. Making \gset rejected in a batch section sounds
> simple enough and supports \beginbatch et al sufficiently to compare
> performance, so I'm OK with a patch that does that. That'd be a small
> extension to your previous patch, if I understand correctly.
>
> If you or others want to send patches to extend batch support with
> read-write tracking for variables, feel free, but I hereby declare that
> I'm not taking immediate responsibility for getting them committed.
I think minimal support is entirely sufficient initially.
Andres
From | Date | Subject | |
---|---|---|---|
Next Message | Vik Fearing | 2020-11-19 00:37:26 | Re: CREATE AGGREGATE array_cat |
Previous Message | Andres Freund | 2020-11-18 22:48:40 | Re: "as quickly as possible" (was: remove spurious CREATE INDEX CONCURRENTLY wait) |