Re: Problems restarting after database crashed (signal 11). - Mailing list pgsql-general

From Greg Stark
Subject Re: Problems restarting after database crashed (signal 11).
Date
Msg-id 873c49w6ae.fsf@stark.xeocode.com
Whole thread Raw
In response to Re: Problems restarting after database crashed (signal 11).  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Problems restarting after database crashed (signal 11).  (Christopher Cashell <topher@zyp.org>)
List pgsql-general
Tom Lane <tgl@sss.pgh.pa.us> writes:

> Christopher Cashell <topher-pgsql@zyp.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.

Is there an NFS server involved? If an NFS server disappears any process
waiting on I/O for it enters disk-wait indefinitely until it reappears.

--
greg

pgsql-general by date:

Previous
From: Mike Nolan
Date:
Subject: Re: Run a unix or perl command in a trigger
Next
From: Tom Lane
Date:
Subject: Re: alter table cascade does not give notice about dropped indexes