Tom,
So you are in agreement that the fix is:
This simple patch seem to fix the problem
--- src/backend/postmaster/postmaster.c.orig 2010-10-27
19:07:42.000000000 +0400
+++ src/backend/postmaster/postmaster.c 2010-10-27 19:08:25.000000000 +0400
@@ -1917,7 +1917,7 @@
if (port->sock >= 0)
StreamClose(port->sock);
ConnFree(port);
- port = NULL;
+ return NULL;
}
else
{
--
>From that previous link?
Sam
-----Original Message-----
From: Tom Lane [mailto:tgl@xxxxxxxxxxxxx]
Sent: Friday, 10 December 2010 3:22 PM
To: Samuel Stearns
Cc: Shoaib Mir; pgsql-admin@xxxxxxxxxxxxxx
Subject: Re: Postgres Crash
Samuel Stearns <SStearns@xxxxxxxxxxxxxxxx> writes:
> Yes, with gssapi.
Well, then we have our smoking gun, but it's still not clear *why*
the setsockopt() call failed.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
