Re: PATCH: Batch/pipelining support for libpq
От | Alvaro Herrera |
---|---|
Тема | Re: PATCH: Batch/pipelining support for libpq |
Дата | |
Msg-id | 20201103134234.GA8821@alvherre.pgsql обсуждение исходный текст |
Ответ на | Re: PATCH: Batch/pipelining support for libpq (Dave Cramer <davecramer@postgres.rocks>) |
Ответы |
Re: PATCH: Batch/pipelining support for libpq
Re: PATCH: Batch/pipelining support for libpq |
Список | pgsql-hackers |
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.
В списке pgsql-hackers по дате отправления: