pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Donald Fraser <postgres@kiwi-fraser.net>
Cc: [ADMIN] <pgsql-admin@postgresql.org>
Subject: Re: Strange message followed by server crash
Date: Fri, 25 Aug 2006 11:24:13 -0400
Message-ID: <20060825152413.GG14622@alvh.no-ip.org> (raw)
In-Reply-To: <24548.1156518324@sss.pgh.pa.us>
References: <003401c6c837$8dc6cb90$7d64a8c0@demolish1>
	<23160.1156513462@sss.pgh.pa.us>
	<008c01c6c855$35f6cd20$7d64a8c0@demolish1>
	<24548.1156518324@sss.pgh.pa.us>

Tom Lane wrote:
> "Donald Fraser" <postgres@kiwi-fraser.net> 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.

Note that on recent versions of Linux you can modify both the file name
and the directory where it's saved, by modifying
/proc/sys/kernel/core_pattern (or the deprecated
/proc/sys/kernel/core_uses_pid).  See core(5) for details.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.



view thread (6+ messages)  latest in thread

Message-ID: <20060825152413.GG14622@alvh.no-ip.org>
Permalink:  ../20060825152413.GG14622@alvh.no-ip.org/
Also on:    postgresql.org/message-id/20060825152413.GG14622@alvh.no-ip.org

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: alvherre@commandprompt.com, tgl@sss.pgh.pa.us, postgres@kiwi-fraser.net
  Subject: Re: Strange message followed by server crash
  In-Reply-To: <20060825152413.GG14622@alvh.no-ip.org>
  References: <003401c6c837$8dc6cb90$7d64a8c0@demolish1> <23160.1156513462@sss.pgh.pa.us> <008c01c6c855$35f6cd20$7d64a8c0@demolish1> <24548.1156518324@sss.pgh.pa.us> <20060825152413.GG14622@alvh.no-ip.org>

* 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