Andres Freund wrote : > If you were to send a gigabyte of queries, it'd buffer them all up in memory... So some >more intelligence is going to be needed.
Firstly, sorry for the delayed response as I got busy with other activities. To buffer up the queries before flushing them to the socket, I think "conn->outCount>=65536" is ok to use, as 64k is considered to be safe in Windows as per comments in pqSendSome() API. Attached the code patch to replace pqFlush calls with pqBatchFlush in the asynchronous libpq function calls flow. Still pqFlush is used in "PQbatchSyncQueue" and "PQexitBatchMode" functions. Am failing to see the benefit in allowing user to set PQBatchAutoFlush(true|false) property? Is it really needed? Thanks & Regards, Vaishnavi, Fujitsu Australia.
0001-Pipelining-batch-support-for-libpq-code-v12.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
