From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Daniel Verite <daniel(at)manitou-mail(dot)org>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: libpq sendQuery -- getResult not returning until all queries complete |
Date: | 2010-12-22 00:03:52 |
Message-ID: | AANLkTinYJyOmwb-TWM1VT4h1Xy4TU6wDUSkp2c+u8Q+L@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Dec 21, 2010 at 6:49 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Merlin Moncure <mmoncure(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Matthias Müller | 2010-12-22 00:10:22 | Re: Understanding PG9.0 streaming replication feature |
Previous Message | Adrian Klaver | 2010-12-22 00:02:22 | Re: plpython returns integer[] fails for multi-dimensional array |