From: Tomasz Myrta <jasiek@klaster.net>
To: Jan Wieck <JanWieck@Yahoo.com>
Cc: Lista dyskusyjna pgsql-sql <pgsql-sql@postgresql.org>
Subject: Re: strange postgresql failure
Date: Thu, 30 Oct 2003 20:14:13 +0100
Message-ID: <3FA16305.7000202@klaster.net> (raw)
In-Reply-To: <3FA14B78.4030904@Yahoo.com>
References: <3FA0F6E9.5060404@klaster.net>
<3FA103AF.1000006@klaster.net>
<3FA14B78.4030904@Yahoo.com>
Dnia 2003-10-30 18:33, Użytkownik Jan Wieck napisał:
> There is, sort of ... it's called "core" and if your backend and C
> function shared object have been compiled with symbol information you
> can use a debugger to get a stack trace and look at variables. If that's
> not "human readable" ... well ... I suppose I'm not human.
I know I can load core into gdb...
I thought about some kind of message before postgres restarts. I read in
syslog that backend terminated with segmentation fault signal and
probably corrupted shared memory. It didn't help me to find what really
happened. I was wondering if it is possible to know the real reason of
restart and leave some message in syslog just before postgres restarts.
Regards,
Tomasz Myrta
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-sql@postgresql.org
Cc: jasiek@klaster.net, JanWieck@Yahoo.com
Subject: Re: strange postgresql failure
In-Reply-To: <3FA16305.7000202@klaster.net>
* 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