Received: from localhost (unknown [200.46.204.184]) by developer.postgresql.org (Postfix) with ESMTP id 7BA462E0046 for ; Mon, 21 Apr 2008 13:54:32 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 41475-03 for ; Mon, 21 Apr 2008 13:54:26 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by developer.postgresql.org (Postfix) with ESMTP id C4F3C2E004D for ; Mon, 21 Apr 2008 13:54:27 -0300 (ADT) Received: from perhan.alvh.no-ip.org (200-126-74-87.bk5-dsl.surnet.cl [200.126.74.87]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m3LGt5p8006787 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 21 Apr 2008 09:55:07 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 1356747C59; Mon, 21 Apr 2008 12:54:24 -0400 (CLT) Date: Mon, 21 Apr 2008 12:54:24 -0400 From: Alvaro Herrera To: Robert Treat Cc: pgsql-performance@postgresql.org Subject: Re: Re: [HACKERS] [COMMITTERS] pgsql: Fix TransactionIdIsCurrentTransactionId() to use binary search Message-ID: <20080421165424.GC14464@alvh.no-ip.org> References: <20080317021856.0D2D37558DC@cvs.postgresql.org> <200803271656.45574.xzilla@users.sourceforge.net> <2092.1206652297@sss.pgh.pa.us> <200804211229.00871.xzilla@users.sourceforge.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200804211229.00871.xzilla@users.sourceforge.net> User-Agent: Mutt/1.5.17+20080114 (2008-01-14) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Mon, 21 Apr 2008 09:55:08 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200804/306 X-Sequence-Number: 29799 Robert Treat wrote: > Unfortunatly I don't have the 8.1 system to bang on anymore for this, (though > anecdotaly speaking, I never saw this behavior in 8.1) however I do now have > a parallel 8.3 system crunching the data, and it is showing the same symptom > (yes, 2 8.3 servers, crunching the same data, both bogged down now), so I do > feel this is something specific to 8.3. > > I am mostly wondering if anyone else has encountered behavior like this on 8.3 > (large sets of insert....update exception block in plpgsql bogging down), or > if anyone has any thoughts on which direction I should poke at it from here. > TIA. Perhaps what you could do is backpatch the change and see if the problem goes away. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.