From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pingu(dot)freak(at)web(dot)de |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Transaction-Overflow |
Date: | 2007-08-07 18:38:44 |
Message-ID: | 26881.1186511924@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
pingu(dot)freak(at)web(dot)de writes:
> On the top in the log file is this, do you know why the pid is killed with =
> 11? I'm a little bit confused :(.
> LOG: Serverprozess (PID 30399) wurde von Signal 11 beendet
SIG 11 (ie SIGSEGV) is pretty much the typical "generic crash"
indication. It most likely means you ran into a software bug or
corrupted data. There is no reason at all to think that it's got
anything to do with transaction ID wraparound --- that message is
only coming out because it always comes out at a database restart.
What you ought to look into is what *did* cause the crash. Did it
produce a core file, and if so can you get a gdb stack trace from
the core?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2007-08-07 19:12:29 | Re: PITR backup to Novell Netware file server |
Previous Message | Decibel! | 2007-08-07 18:30:03 | Re: Transaction-Overflow |