X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 0BA299FBB06 for ; Fri, 25 Aug 2006 12:05:40 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 73999-01 for ; Fri, 25 Aug 2006 15:05:31 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 78A2F9FBB05 for ; Fri, 25 Aug 2006 12:05:31 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k7PF5Ohx024549; Fri, 25 Aug 2006 11:05:24 -0400 (EDT) To: "Donald Fraser" cc: "[ADMIN]" Subject: Re: Strange message followed by server crash In-reply-to: <008c01c6c855$35f6cd20$7d64a8c0@demolish1> References: <003401c6c837$8dc6cb90$7d64a8c0@demolish1> <23160.1156513462@sss.pgh.pa.us> <008c01c6c855$35f6cd20$7d64a8c0@demolish1> Comments: In-reply-to "Donald Fraser" message dated "Fri, 25 Aug 2006 15:46:11 +0100" Date: Fri, 25 Aug 2006 11:05:24 -0400 Message-ID: <24548.1156518324@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200608/288 X-Sequence-Number: 22831 "Donald Fraser" writes: > "Tom Lane" writes: >> Given that this sounds like it won't be easy to reproduce, I'm hoping >> you have a core file left from that and can get a stack trace from it. > Where would I look for a core file? > There's nothing unusual in the data directory, nothing in the /tmp = > directory? Normally it would go into the $PGDATA/base/NNN subdirectory for the database the backend was connected to. A very few systems (OS X for instance) drop cores into a dedicated system-wide directory called /cores or some such. If you're not finding anything, it's probably because the postmaster was launched under "ulimit -c 0" or local equivalent spelling --- a lot of systems have a policy of launching daemons that way. > If there isn't a core file, how would I go about ensuring one is created = > next time? (touch wood there wont be one). Put "ulimit -c unlimited" into the script that launches the postmaster, and restart it. regards, tom lane