From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Dave Cramer <davecramer@postgres.rocks>
Cc: Matthieu Garrigues <matthieu.garrigues@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PATCH: Batch/pipelining support for libpq
Date: Tue, 3 Nov 2020 10:42:34 -0300
Message-ID: <20201103134234.GA8821@alvherre.pgsql> (raw)
In-Reply-To: <CADK3HHKZ5uagbFs2-VFyQU30+VOVZ30VdU-4UQkrSmFkT-tFbQ@mail.gmail.com>
Hi Dave,
On 2020-Nov-03, Dave Cramer wrote:
> On Mon, 2 Nov 2020 at 10:57, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
>
> > On 2020-Nov-02, Alvaro Herrera wrote:
> >
> > > In v23 I've gone over docs; discovered that PQgetResults docs were
> > > missing the new values. Added those. No significant other changes yet.
>
> Thanks for looking at this.
>
> What else does it need to get it in shape to apply?
I want to go over the code in depth to grok the design more fully.
It would definitely help if you (and others) could think about the API
being added: Does it fulfill the promises being made? Does it offer the
guarantees that real-world apps want to have? I'm not much of an
application writer myself -- particularly high-traffic apps that would
want to use this. As a driver author I would welcome your insight in
these questions.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: alvherre@alvh.no-ip.org, davecramer@postgres.rocks, matthieu.garrigues@gmail.com, michael@paquier.xyz
Subject: Re: PATCH: Batch/pipelining support for libpq
In-Reply-To: <20201103134234.GA8821@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox