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
