Re: [GENERAL] Pipelining INSERTs using libpq

2012-12-23 Thread Merlin Moncure
On Sunday, December 23, 2012, Tom Lane wrote: > Florian Weimer writes: >> Does the wire protocol support pipelining? > > Yes, but libpq doesn't really expose the capability, because it's too > simple-minded to deal with more than one query in flight. > > regards, tom lane

Re: [GENERAL] Pipelining INSERTs using libpq

2012-12-23 Thread Tom Lane
Florian Weimer writes: > Does the wire protocol support pipelining? Yes, but libpq doesn't really expose the capability, because it's too simple-minded to deal with more than one query in flight. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@p

Re: [GENERAL] Pipelining INSERTs using libpq

2012-12-23 Thread Florian Weimer
On 12/21/2012 03:29 PM, Merlin Moncure wrote: How you attack this problem depends a lot on if all your data you want to insert is available at once or you have to wait for it from some actor on the client side. The purpose of asynchronous API is to allow client side work to continue while the se

Re: [GENERAL] Pipelining INSERTs using libpq

2012-12-21 Thread Merlin Moncure
On Fri, Dec 21, 2012 at 4:31 AM, Florian Weimer wrote: > I would like to pipeline INSERT statements. The idea is to avoid waiting > for server round trips if the INSERT has no RETURNING clause and runs in a > transaction. In my case, the failure of an individual INSERT is not > particularly inte

[GENERAL] Pipelining INSERTs using libpq

2012-12-21 Thread Florian Weimer
I would like to pipeline INSERT statements. The idea is to avoid waiting for server round trips if the INSERT has no RETURNING clause and runs in a transaction. In my case, the failure of an individual INSERT is not particularly interesting (it's a "can't happen" scenario, more or less). I b