Re: "incomplete startup packet" on SGI - Mailing list pgsql-general

From David Rysdam
Subject Re: "incomplete startup packet" on SGI
Date
Msg-id 43A02B88.208@ll.mit.edu
Whole thread Raw
In response to Re: "incomplete startup packet" on SGI  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: "incomplete startup packet" on SGI
List pgsql-general
Tom Lane wrote:

>David Rysdam <drysdam@ll.mit.edu> writes:
>
>
>>Just finished building and installing on *Sun* (also
>>"--without-readline", not that I think that could be the issue): Works
>>fine.  So it's something to do with the SGI build in particular.
>>
>>
>
>More likely it's something to do with weird behavior of the SGI kernel's
>TCP stack.  I did a little googling for "transport endpoint is not
>connected" without turning up anything obviously related, but that or
>ENOTCONN is probably what you need to search on.
>
>            regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 2: Don't 'kill -9' the postmaster
>
>
>
>
It's acting like a race condition or pointer problem.  When I add random
debug printfs/PQflushs to libpq it sometimes works.

pgsql-general by date:

Previous
From: hubert depesz lubaczewski
Date:
Subject: outdated (bad) information in pg_stat_activity
Next
From: Tom Lane
Date:
Subject: Re: valgrind output