Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id EA2951337B5E for ; Fri, 10 Dec 2010 00:52:38 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 45848-02 for ; Fri, 10 Dec 2010 04:52:31 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 7D43713364DE for ; Fri, 10 Dec 2010 00:52:31 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id oBA4qOod014435; Thu, 9 Dec 2010 23:52:25 -0500 (EST) To: Samuel Stearns cc: Shoaib Mir , "pgsql-admin@postgresql.org" Subject: Re: Postgres Crash In-reply-to: <68B59BEDCD36854AADBDF17E91B2937A07844CD061@EXCHMAIL.staff.internode.com.au> References: <68B59BEDCD36854AADBDF17E91B2937A07844CD029@EXCHMAIL.staff.internode.com.au> <68B59BEDCD36854AADBDF17E91B2937A07844CD02E@EXCHMAIL.staff.internode.com.au> <13055.1291952802@sss.pgh.pa.us> <68B59BEDCD36854AADBDF17E91B2937A07844CD04D@EXCHMAIL.staff.internode.com.au> <13945.1291954973@sss.pgh.pa.us> <68B59BEDCD36854AADBDF17E91B2937A07844CD059@EXCHMAIL.staff.internode.com.au> <14104.1291955542@sss.pgh.pa.us> <68B59BEDCD36854AADBDF17E91B2937A07844CD061@EXCHMAIL.staff.internode.com.au> Comments: In-reply-to Samuel Stearns message dated "Fri, 10 Dec 2010 15:10:53 +1030" Date: Thu, 09 Dec 2010 23:52:24 -0500 Message-ID: <14434.1291956744@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_FRT_STOCK2=0.01, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201012/73 X-Sequence-Number: 36302 Samuel Stearns 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