From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Daniel Verite <daniel(at)manitou-mail(dot)org> |
Cc: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, vaishnaviprabakaran(at)gmail(dot)com, michael(dot)paquier(at)gmail(dot)com, daniel(at)yesql(dot)se, craig(at)2ndquadrant(dot)com, andres(at)anarazel(dot)de, david(at)pgmasters(dot)net, VaishnaviP(at)fast(dot)au(dot)fujitsu(dot)com, kommi(dot)haribabu(at)gmail(dot)com, tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com, dmitigr(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org, m(dot)kniep(at)web(dot)de, fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp, iwata(dot)aya(at)jp(dot)fujitsu(dot)com |
Subject: | Re: [HACKERS] PATCH: Batch/pipelining support for libpq |
Date: | 2018-10-01 06:34:17 |
Message-ID: | 20181001063417.GC11712@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Mar 23, 2018 at 02:18:09PM +0100, Daniel Verite wrote:
> There's a batch mode for pgbench in a patch posted in [1],
> with \beginbatch and \endbatch commands, but nothing
> for psql AFAICS.
> psql is more complicated because currently it uses a
> blocking PQexec() call at its core. Craig mentioned psql
> integration in [2] and [3].
This patch has been around for some time now, the last version fails to
apply cleanly and in-depth reviews have happened. I am moving that to
the next CF, waiting on its author.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2018-10-01 06:36:52 | Re: Adding a note to protocol.sgml regarding CopyData |
Previous Message | Michael Paquier | 2018-10-01 06:30:06 | Re: Sample values for pg_stat_statements |