Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id A0EDF1337B91 for ; Fri, 10 Dec 2010 00:21:33 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 22840-04 for ; Fri, 10 Dec 2010 04:21:26 +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 335481337B8E for ; Fri, 10 Dec 2010 00:21:26 -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 oBA4LIXH013890; Thu, 9 Dec 2010 23:21:18 -0500 (EST) To: Samuel Stearns cc: Shoaib Mir , "pgsql-admin@postgresql.org" Subject: Re: Postgres Crash In-reply-to: <68B59BEDCD36854AADBDF17E91B2937A07844CD04A@EXCHMAIL.staff.internode.com.au> References: <68B59BEDCD36854AADBDF17E91B2937A07844CD029@EXCHMAIL.staff.internode.com.au> <68B59BEDCD36854AADBDF17E91B2937A07844CD02E@EXCHMAIL.staff.internode.com.au> <13055.1291952802@sss.pgh.pa.us> <68B59BEDCD36854AADBDF17E91B2937A07844CD04A@EXCHMAIL.staff.internode.com.au> Comments: In-reply-to Samuel Stearns message dated "Fri, 10 Dec 2010 14:35:12 +1030" Date: Thu, 09 Dec 2010 23:21:18 -0500 Message-ID: <13889.1291954878@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/68 X-Sequence-Number: 36297 Samuel Stearns writes: > [root@udrv] # pstack /root/core > core '/root/core' of 771: /opt/postgres/8.3-community/bin/postmaster -F > 081a8562 ConnCreate (5) + b6 > 081a791b ServerLoop (8047e68, 83b7930, 2, fead58be, 8047e68, 83c28b8) + db > 081a73f1 PostmasterMain (2, 83b7930) + ab5 > 08164e3a main (2, 8047e44, 8047e50) + 17a > 080891fa _start (2, 8047ed0, 8047efb, 0, 8047efe, 8047f2e) + 7a Hmmm ... does your build have GSS enabled (configure --with-gssapi)? If so I think you ran into this recently-discovered issue: http://archives.postgresql.org/pgsql-committers/2010-10/msg00253.php I had originally thought that your log message about setsockopt(TCP_NODELAY) failed: Invalid argument was post-crash, but if it was pre-crash it supports that theory, because that error would in fact lead to the core dump in ConnCreate if you had ENABLE_GSS on. In any case that log message is pretty odd: it's not at all clear how the setsockopt call could have failed. Failure to establish a socket should bail out earlier. regards, tom lane