Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id BFC329F9CCC for ; Thu, 16 Nov 2006 14:10:44 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 97943-01 for ; Thu, 16 Nov 2006 14:10:41 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 0937E9F9998 for ; Thu, 16 Nov 2006 14:10:40 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id kAGIAVva019529; Thu, 16 Nov 2006 13:10:32 -0500 (EST) To: Richard Huxton cc: "Craig A. James" , Russell Smith , pgsql-performance@postgresql.org Subject: Re: Postgres server crash In-reply-to: <455CA016.7030709@archonet.com> References: <20061023215913.GW26892@nasby.net> <20061025001709.GA26892@nasby.net> <453EF7C4.2040105@modgraph-usa.com> <455BCAE8.8010905@modgraph-usa.com> <455BCCCD.2020701@pws.com.au> <455C420D.8090209@archonet.com> <455C9CCA.7080804@modgraph-usa.com> <455CA016.7030709@archonet.com> Comments: In-reply-to Richard Huxton message dated "Thu, 16 Nov 2006 17:29:58 +0000" Date: Thu, 16 Nov 2006 13:10:31 -0500 Message-ID: <19528.1163700631@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/125 X-Sequence-Number: 21895 Richard Huxton writes: > Craig A. James wrote: >> It can't be a coincidence that these were the only two processes in a >> SELECT operation. Does the server disable signals at critical points? > If a "kill -9" as root doesn't get rid of them, I think I'm right in > saying that it's a kernel-level problem rather than something else. I didn't actually see Craig say anywhere that he'd tried "kill -9" on those backends. If he did and it didn't do anything, then clearly they were in some kind of uninterruptable wait, which is certainly evidence of a kernel or hardware issue. If he didn't do "kill -9" then we don't really know what the issue was --- it's not improbable that they were stuck in some loop not containing a CHECK_FOR_INTERRUPTS() test. regards, tom lane