On Mon, Jul 05, 2004 at 10:43:47PM -0400, Tom Lane wrote:
> L J Bayuk <ljb220@xxxxxxxxxxxxxx> writes:
> > The delay we are seeing (about 40 ms) is from the time the client sends the
> > Bind message to PostgreSQL until it gets a TCP ACK back. (It should get
> > a BindComplete message back, but the backend doesn't flush after sending
> > this - no pq_flush() at the end of exec_bind_message(). Hello, Tom, is this
> > a bug?
>
> No. If you wanted a flush just there, send a Flush message. But AFAICS
> the only reason why you'd do that is if you needed to look at the
> BindComplete before sending your next message --- which you do not.
I agree, it works OK as is. I only raised the question because of two
things. First, the protocol documentation says:
"The response (to the Bind message) is either BindComplete
or ErrorResponse."
|
