Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id CD6139FBB72 for ; Wed, 2 May 2007 09:59:51 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 61451-05 for ; Wed, 2 May 2007 09:59:38 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id DDCB99FB7D9 for ; Wed, 2 May 2007 09:59:48 -0300 (ADT) Received: from perhan.alvh.no-ip.org (201-221-217-243.bk12-dsl.surnet.cl [201.221.217.243]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l42CxgOM025565; Wed, 2 May 2007 05:59:43 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id C03E132A10; Wed, 2 May 2007 08:59:40 -0400 (CLT) Date: Wed, 2 May 2007 08:59:40 -0400 From: Alvaro Herrera To: Thomas Markus Cc: pgsql-admin@postgresql.org Subject: Re: infinite blocking statements in 8.2.3 Message-ID: <20070502125940.GC4585@alvh.no-ip.org> Mail-Followup-To: Thomas Markus , pgsql-admin@postgresql.org References: <46384CEA.9080906@proventis.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46384CEA.9080906@proventis.net> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: ClamAV version 0.88.5, clamav-milter version 0.88.5 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Wed, 02 May 2007 05:59:48 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/16 X-Sequence-Number: 25336 Thomas Markus wrote: > I'm running 8.2.3 on ubuntu 6.06 (2.6.15-26-server SMP i686) > > sometimes i have SELECTs that never ends. Normally I drop connections by > killing the connection process (kill ). But these hanging > connections (which blocks other statements infinitly) cant be killed. What are they doing? We've added interrupt checks in most of the loops, so queries can normally be killed quickly, but maybe we've missed just the one you're running. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support