Samuel Stearns <SStearns@xxxxxxxxxxxxxxxx> 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 -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
