Skip site navigation (1) Skip section navigation (2)

Re: Postgres Crash

From: Samuel Stearns <SStearns(at)internode(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Shoaib Mir <shoaibmir(at)gmail(dot)com>, "pgsql-admin(at)postgresql(dot)org"<pgsql-admin(at)postgresql(dot)org>
Subject: Re: Postgres Crash
Date: 2010-12-10 04:57:14
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin

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)
-               port = NULL;
+               return NULL;


From that previous link?


-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us] 
Sent: Friday, 10 December 2010 3:22 PM
To: Samuel Stearns
Cc: Shoaib Mir; pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] Postgres Crash 

Samuel Stearns <SStearns(at)internode(dot)com(dot)au> 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

In response to

pgsql-admin by date

Next:From: Samuel StearnsDate: 2010-12-10 05:00:46
Subject: Re: Postgres Crash
Previous:From: Tom LaneDate: 2010-12-10 04:52:24
Subject: Re: Postgres Crash

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group