pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Tom Lane <tgl@sss.pgh.pa.us>
To: Samuel Stearns <SStearns@internode.com.au>
Cc: Shoaib Mir <shoaibmir@gmail.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Postgres Crash
Date: Thu, 09 Dec 2010 23:21:18 -0500
Message-ID: <13889.1291954878@sss.pgh.pa.us> (raw )
In-Reply-To: <68B59BEDCD36854AADBDF17E91B2937A07844CD04A@EXCHMAIL.staff.internode.com.au >
References: <68B59BEDCD36854AADBDF17E91B2937A07844CD029@EXCHMAIL.staff.internode.com.au >
<AANLkTikYRT15R61-ZByCzs_PoMT50JHbQFWeymeYjtjn@mail.gmail.com >
<68B59BEDCD36854AADBDF17E91B2937A07844CD02E@EXCHMAIL.staff.internode.com.au >
<13055.1291952802@sss.pgh.pa.us >
<68B59BEDCD36854AADBDF17E91B2937A07844CD04A@EXCHMAIL.staff.internode.com.au >
Samuel Stearns <SStearns@internode.com.au> 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
view thread (22+ messages) latest in thread
Message-ID: <13889.1291954878@sss.pgh.pa.us>
Permalink: ../13889.1291954878@sss.pgh.pa.us/
Also on: postgresql.org/message-id/13889.1291954878@sss.pgh.pa.us
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, SStearns@internode.com.au, shoaibmir@gmail.com
Subject: Re: Postgres Crash
In-Reply-To: <13889.1291954878@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox