Jeremy Ashcraft <jashcraft@xxxxxxxxxx> 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
