Re: libpq sendQuery -- getResult not returning until all queries complete
| От | Merlin Moncure |
|---|---|
| Тема | Re: libpq sendQuery -- getResult not returning until all queries complete |
| Дата | |
| Msg-id | AANLkTinYJyOmwb-TWM1VT4h1Xy4TU6wDUSkp2c+u8Q+L@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: libpq sendQuery -- getResult not returning until all queries complete (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: libpq sendQuery -- getResult not returning until all queries complete
|
| Список | pgsql-general |
On Tue, Dec 21, 2010 at 6:49 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Merlin Moncure <mmoncure@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
В списке pgsql-general по дате отправления: