Re: "incomplete startup packet" on SGI

From: David Rysdam <drysdam(at)ll(dot)mit(dot)edu>
To:
Cc: "pg >> Postgres General" <pgsql-general(at)postgresql(dot)org>
Subject: Re: "incomplete startup packet" on SGI
Date: 2005-12-14 14:26:16
Message-ID: 43A02B88.208@ll.mit.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane wrote:

>David Rysdam <drysdam(at)ll(dot)mit(dot)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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2005-12-14 15:11:14 Re: valgrind output
Previous Message hubert depesz lubaczewski 2005-12-14 14:02:48 outdated (bad) information in pg_stat_activity