| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jeremy Ashcraft <jashcraft(at)edgate(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: strange hung processes |
| Date: | 2006-02-03 04:47:20 |
| Message-ID: | 22802.1138942040@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Jeremy Ashcraft <jashcraft(at)edgate(dot)com> writes:
> in /proc
> codd 13262 # cat status {proc "filesystem"}
> Name: postmaster
> State: D (disk sleep)
> Because of the "D" state, it can't be killed as it is not interuptible
> (waiting on IO ?).
If the process is stuck in D state then it's not Postgres' fault.
You're looking at a hardware problem, or if the database is mounted
via NFS then it might be an NFS-protocol-level problem. In any case
you need to call out the kernel and hardware troops, not us database
weenies ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Lutterkort | 2006-02-03 23:48:35 | su-like behavior |
| Previous Message | Michael Fuhr | 2006-02-03 03:17:17 | Re: is there any missing ?? |