Horton

Re: PATCH: Batch/pipelining support for libpq

Jim Nasby <jim.nasby@bluetreble.com>

View thread View on postgr.es
From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: Michael Paquier <michael.paquier@gmail.com>, Craig Ringer <craig@2ndquadrant.com>
Cc: Daniel Verite <daniel@manitou-mail.org>, Dmitry Igrishin <dmitigr@gmail.com>, Andres Freund <andres@anarazel.de>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Manuel Kniep <m.kniep@web.de>, "fujita.etsuro@lab.ntt.co.jp" <fujita.etsuro@lab.ntt.co.jp>
Date: 2016-10-14T01:04:14Z
Lists: pgsql-hackers 
On 10/4/16 11:54 PM, Michael Paquier wrote:
> +   <para>
> +    Much like asynchronous query mode, there is no performance disadvantage to
> +    using batching and pipelining. It somewhat increased client application
> +    complexity and extra caution is required to prevent client/server network
> +    deadlocks, but can offer considerable performance improvements.
> +   </para>
> I would reword that a bit "it increases client application complexity
> and extra caution is required to prevent client/server deadlocks but
> offers considerable performance improvements".

Unrelated, but another doc bug, on line 4647:

  +     The batch API was introduced in PostgreSQL 9.6, but clients 
using it can

That should read 10.0 (or just 10?)
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)   mobile: 512-569-9461

Commits

  1. Add libpq pipeline mode support to pgbench

  2. Implement pipeline mode in libpq