X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 5A12F9F9EEB for ; Tue, 23 May 2006 04:04:45 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 15737-05 for ; Tue, 23 May 2006 04:04:36 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from astro.systems.pipex.net (astro.systems.pipex.net [62.241.163.6]) by postgresql.org (Postfix) with ESMTP id 280239F9CAA for ; Tue, 23 May 2006 04:04:35 -0300 (ADT) Received: from flange.edesix.com (81-86-64-114.dsl.pipex.com [81.86.64.114]) by astro.systems.pipex.net (Postfix) with ESMTP id EB197E00047B; Tue, 23 May 2006 08:04:31 +0100 (BST) Received: from host81-153-246-73.range81-153.btcentralplus.com ([81.153.246.73] helo=[192.168.101.208]) by flange.edesix.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.60) (envelope-from ) id 1FiQwQ-0001yI-PT; Tue, 23 May 2006 08:04:30 +0100 Message-ID: <4472B40B.1080005@edesix.com> Date: Tue, 23 May 2006 08:04:43 +0100 From: Robin Iddon User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: "Thomas F. O'Connell" CC: pgsql-admin@postgresql.org Subject: Re: Unkillable Backend Processes References: <3BB218ED-FD62-42BF-8BDD-066954F961AC@sitening.com> In-Reply-To: <3BB218ED-FD62-42BF-8BDD-066954F961AC@sitening.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/304 X-Sequence-Number: 21836 > > 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