Re: LOG: unexpected EOF within message length word

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Fuhr <mike(at)fuhr(dot)org>
Cc: "Mavinakuli, Prasanna (STSD)" <prasanna(dot)b-m(at)hp(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: LOG: unexpected EOF within message length word
Date: 2005-09-03 15:44:43
Message-ID: 26745.1125762283@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Michael Fuhr <mike(at)fuhr(dot)org> writes:
> On Sat, Sep 03, 2005 at 11:31:19AM +0530, Mavinakuli, Prasanna (STSD) wrote:
>> 1) I am using postgres 7.4 version.

> Exactly which version?

I'm wondering about the relevance of this pre-7.4-final bug fix:

2003-10-19 17:36 tgl

* src/interfaces/libpq/: fe-exec.c, fe-misc.c: Adjust libpq to
avoid deadlock when both client and server want to send data, and
both have filled the transmission buffers. One scenario where this
can happen was illustrated here:
http://archives.postgresql.org/pgsql-hackers/2003-04/msg00979.php

Supposing that a 7.4-beta libpq were in use, and for some reason the
server tries to send a large reply message before it's absorbed all
of the command, we could see a hangup like this. It'd be useful to
see an strace of the server process in parallel with the client.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Michael Fuhr 2005-09-03 15:49:44 Re: Schema problems RedHat / SuSE 9.3 for version 7.4.8
Previous Message Michael Fuhr 2005-09-03 14:42:03 Re: LOG: unexpected EOF within message length word