X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id B05A3D1B189 for ; Tue, 8 Jun 2004 11:24:48 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 76541-10 for ; Tue, 8 Jun 2004 14:24:48 +0000 (GMT) Received: from ml-hw5.monsterlabs.com (ml-hw5.monsterlabs.com [216.183.105.167]) by svr1.postgresql.org (Postfix) with SMTP id 4E8A5D1B19D for ; Tue, 8 Jun 2004 11:24:40 -0300 (ADT) Received: (qmail 7051 invoked from network); 8 Jun 2004 14:24:40 -0000 Received: from w080.z064003242.bna-tn.dsl.cnc.net (HELO ?192.168.1.15?) (64.3.242.80) by ml-hw5.monsterlabs.com with SMTP; 8 Jun 2004 14:24:40 -0000 From: Marcus Whitney Reply-To: marcus@coldfeetcreative.com Organization: Coldfeet Creative To: Tom Lane Subject: Re: pl/pgsql and Transaction Isolation Date: Tue, 8 Jun 2004 09:19:44 -0500 User-Agent: KMail/1.6.1 References: <200406071131.46488.marcus@coldfeetcreative.com> <25924.1086668975@sss.pgh.pa.us> In-Reply-To: <25924.1086668975@sss.pgh.pa.us> Cc: pgsql-performance@postgresql.org MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406080919.45031.marcus@coldfeetcreative.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200406/87 X-Sequence-Number: 7145 You were right not to believe it. I had an update on a whole table that I hadn't noticed. Thanks for debunking. On Monday 07 June 2004 23:29, you wrote: > Marcus Whitney writes: > > I have an instance where I have a series of pl/pgsql calls, that report > > stat results to a common table. When other queries try to hit the stat > > table (with DML commands; SELECT, INSERT, UPDATE, DELETE etc.) they are > > forced to wait in a queue until the pl/pgsql has finished executing. > > This is quite hard to believe, unless your pl/pgsql is doing something > as unfriendly as LOCKing the table. > > Do you want to post a more complete description of your problem? > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org -- marcus whitney