From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Christopher Cashell <topher-pgsql(at)zyp(dot)org> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Problems restarting after database crashed (signal 11). |
Date: | 2004-07-01 01:54:26 |
Message-ID: | 17665.1088646866@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Christopher Cashell <topher-pgsql(at)zyp(dot)org> writes:
> Eventually I attempted to shut it down and restart it, however that
> failed too. When I attempted to shut it down, I discovered a hung
> 'startup subprocess' that can't be killed.
This is interesting because it seems just about exactly like this
recent Red Hat bug report:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=126885
As I commented there, I think that it must be a kernel or hardware
issue --- Postgres itself can surely not make an unkillable process.
However it's common to see processes that don't respond to kill if
they are stuck inside a kernel I/O request. That could mean either
unresponsive hardware or a kernel bug.
I wonder whether you have any similarities in hardware or Linux kernel
to the person who filed the above report?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Cashell | 2004-07-01 02:37:58 | Re: Problems restarting after database crashed (signal 11). |
Previous Message | Tom Lane | 2004-07-01 01:38:08 | Re: case for lock_timeout |