pg.ddx.io pgsql-sql@postgresql.org mailing list archive
help / color / mirror / Atom feedstrange postgresql failure
4+ messages / 2 participants
[nested] [flat]
* strange postgresql failure
@ 2003-10-30 11:32 Tomasz Myrta <jasiek@klaster.net>
0 siblings, 1 reply; 4+ messages in thread
From: Tomasz Myrta @ 2003-10-30 11:32 UTC (permalink / raw)
To: pgsql-sql
postgres[666]: [1] LOG: server process (pid 3166) was terminated by
signal 11
postgres[666]: [2] LOG: terminating any other active server processes
postgres[806]: [591-1] WARNING: Message from PostgreSQL backend:
postgres[806]: [591-2] ^IThe Postmaster has informed me that some
other backend
billy postgres[806]: [591-3] ^Idied abnormally and possibly corrupted
shared memory.
billy postgres[806]: [591-4] ^II have rolled back the current
transaction and am
billy postgres[806]: [591-5] ^Igoing to terminate your database system
connection and exit.
billy postgres[806]: [591-6] ^IPlease reconnect to the database system
and repeat your query.
After few seconds all backends were disconnected and postgres restarted.
It didn't help :-( Even reboot didn't help...
Postgres is 7.3.2-2 on Debian Woody.
Regards,
Tomasz Myrta
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: strange postgresql failure
@ 2003-10-30 12:27 Tomasz Myrta <jasiek@klaster.net>
parent: Tomasz Myrta <jasiek@klaster.net>
0 siblings, 1 reply; 4+ messages in thread
From: Tomasz Myrta @ 2003-10-30 12:27 UTC (permalink / raw)
To: pgsql-sql
Dnia 2003-10-30 12:32, Użytkownik Tomasz Myrta napisał:
> After few seconds all backends were disconnected and postgres restarted.
> It didn't help :-( Even reboot didn't help...
>
> Postgres is 7.3.2-2 on Debian Woody.
Sorry for my panic. It was my C function which raised segmentation fault.
Anyway it would be nice to have some human readable control over C
functions...
Regards,
Tomasz Myrta
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: strange postgresql failure
@ 2003-10-30 17:33 Jan Wieck <JanWieck@Yahoo.com>
parent: Tomasz Myrta <jasiek@klaster.net>
0 siblings, 1 reply; 4+ messages in thread
From: Jan Wieck @ 2003-10-30 17:33 UTC (permalink / raw)
To: Tomasz Myrta <jasiek@klaster.net>; +Cc: pgsql-sql
Tomasz Myrta wrote:
> Dnia 2003-10-30 12:32, Użytkownik Tomasz Myrta napisał:
>> After few seconds all backends were disconnected and postgres restarted.
>> It didn't help :-( Even reboot didn't help...
>>
>> Postgres is 7.3.2-2 on Debian Woody.
>
> Sorry for my panic. It was my C function which raised segmentation fault.
>
> Anyway it would be nice to have some human readable control over C
> functions...
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.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck@Yahoo.com #
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: strange postgresql failure
@ 2003-10-30 19:14 Tomasz Myrta <jasiek@klaster.net>
parent: Jan Wieck <JanWieck@Yahoo.com>
0 siblings, 0 replies; 4+ messages in thread
From: Tomasz Myrta @ 2003-10-30 19:14 UTC (permalink / raw)
To: Jan Wieck <JanWieck@Yahoo.com>; +Cc: pgsql-sql
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
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2003-10-30 19:14 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2003-10-30 11:32 strange postgresql failure Tomasz Myrta <jasiek@klaster.net>
2003-10-30 12:27 ` Tomasz Myrta <jasiek@klaster.net>
2003-10-30 17:33 ` Jan Wieck <JanWieck@Yahoo.com>
2003-10-30 19:14 ` Tomasz Myrta <jasiek@klaster.net>
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