From: Robin Iddon <robin@edesix.com>
To: Thomas F. O'Connell <tfo@sitening.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Unkillable Backend Processes
Date: Tue, 23 May 2006 08:04:43 +0100
Message-ID: <4472B40B.1080005@edesix.com> (raw)
In-Reply-To: <3BB218ED-FD62-42BF-8BDD-066954F961AC@sitening.com>
References: <3BB218ED-FD62-42BF-8BDD-066954F961AC@sitening.com>
>
> There's also an NFS mount point.
>
It's a long time since I used NFS but when I last did you had the choice
between hard and soft mounts. A hard mount would behave like a physical
drive (and would more-or-less never give up trying to commit a write)
while a soft mount would return an error to the calling process should
the mount become unavailable.
Next time this happens you should be able to run
ps -eo pid,wchan,user,args -u postgres
Or similar (you need the wchan somehow or other - top can show it to,
but I cannot remember the letter to toggle its display :-)), and
obviously I assume that postgres is the user pg runs under.
Your rogue process should show up a system call in the wchan column,
and if you keep listing the process it won't change. This shows you are
stuck (and also the args should show you at least whether it's INSERT or
SELECT etc.).
Even if your NFS mount doesn't have pg stuff on it, it could cause
problems if you manage to stop a process in the kernel that has locked a
resource that pg ends up needing (but I don't see this as likely because
I would imagine a long queue of other processes backing up in the same way).
Unless you really need the NFS mount I might be inclined to turn it off
for a while and see what happens ...
Cheers,
Robin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: robin@edesix.com, tfo@sitening.com
Subject: Re: Unkillable Backend Processes
In-Reply-To: <4472B40B.1080005@edesix.com>
References: <3BB218ED-FD62-42BF-8BDD-066954F961AC@sitening.com> <4472B40B.1080005@edesix.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox