Re: Problems restarting after database crashed (signal 11).

From: Greg Stark <gsstark(at)mit(dot)edu>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Problems restarting after database crashed (signal 11).
Date: 2004-07-03 13:48:25
Message-ID: 873c49w6ae.fsf@stark.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> 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.

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2004-07-03 15:16:12 Re: alter table cascade does not give notice about dropped indexes
Previous Message Mike Nolan 2004-07-03 13:33:47 Re: Run a unix or perl command in a trigger