On Tue, Dec 21, 2010 at 6:49 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Merlin Moncure <mmonc...@gmail.com> writes: >> hm, a pq_flush() after command completion putmessage in >> backend/tcop/dest.c seems to fix the problem. I'll send up a patch to >> -hackers. They might backpatch it, unless there is a good reason not >> to do this (I can't think of any). > > If you just unconditionally flush there, it will result in an extra > network message in the normal case where there's not another query > to do. The current code is designed not to flush until it sends > ReadyForQuery.
yeah, I was looking at that. I don't see an easy way to test if there is another query waiting to execute right there. Maybe a documentation patch is in order :-). merlin -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
