| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Dave Cramer <davecramer(at)postgres(dot)rocks> |
| Cc: | Matthieu Garrigues <matthieu(dot)garrigues(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PATCH: Batch/pipelining support for libpq |
| Date: | 2020-11-03 13:42:34 |
| Message-ID: | 20201103134234.GA8821@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Dave,
On 2020-Nov-03, Dave Cramer wrote:
> On Mon, 2 Nov 2020 at 10:57, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2020-11-03 14:27:04 | Re: psql \df choose functions by their arguments |
| Previous Message | Dave Cramer | 2020-11-03 13:20:03 | Re: PATCH: Batch/pipelining support for libpq |