From: | Christopher Cashell <topher-pgsql(at)zyp(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Problems restarting after database crashed (signal 11). |
Date: | 2004-07-01 07:26:25 |
Message-ID: | 20040701072625.GA5380@zyp.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
At Wed, 30 Jun 04, Unidentified Flying Banana Tom Lane, said:
> Christopher Cashell <topher-pgsql(at)zyp(dot)org> writes:
> > 28424 postgres 18 0 16804 3044 15m D 0.0 1.6 0:06.72 postmaster
>
> > Note that it does have a process status of 'D', or uninterruptible
> > sleep. That would explain the unkillable part, though I'm curious how
> > it ended up there.
>
> Perhaps I'm just of an older generation, but I always thought 'D' meant
> "disk I/O wait". Which definitely is uninterruptible on most Unixen.
I've always heard it as 'uninteruptable sleep', which I understood to be
the generic term description, and that 'disk I/O wait' is the most
common cause for it (but not the only possible cause).
Either way, I think you're right, and I think that is what happened
here.
> regards, tom lane
--
| Christopher
+------------------------------------------------+
| Here I stand. I can do no other. |
+------------------------------------------------+
From | Date | Subject | |
---|---|---|---|
Next Message | Shridhar Daithankar | 2004-07-01 07:31:23 | Re: Dump / restore for optimization? |
Previous Message | Scott Marlowe | 2004-07-01 05:35:43 | Re: Problems restarting after database crashed (signal |