From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Donald Fraser <postgres(at)kiwi-fraser(dot)net>, "[ADMIN]" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Strange message followed by server crash |
Date: | 2006-08-25 15:24:13 |
Message-ID: | 20060825152413.GG14622@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Tom Lane wrote:
> "Donald Fraser" <postgres(at)kiwi-fraser(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Jeanna Geier | 2006-08-25 18:20:42 | Issue With Restoring a Dump |
Previous Message | Tom Lane | 2006-08-25 15:05:24 | Re: Strange message followed by server crash |