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 4C7B0D1B44E for ; Tue, 8 Jun 2004 01:29:47 -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 05830-09 for ; Tue, 8 Jun 2004 04:29:39 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id C5C3AD1B276 for ; Tue, 8 Jun 2004 01:29:37 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i584TZAM025925; Tue, 8 Jun 2004 00:29:35 -0400 (EDT) To: marcus@coldfeetcreative.com Cc: pgsql-performance@postgresql.org Subject: Re: pl/pgsql and Transaction Isolation In-reply-to: <200406071131.46488.marcus@coldfeetcreative.com> References: <200406071131.46488.marcus@coldfeetcreative.com> Comments: In-reply-to Marcus Whitney message dated "Mon, 07 Jun 2004 11:31:46 -0500" Date: Tue, 08 Jun 2004 00:29:35 -0400 Message-ID: <25924.1086668975@sss.pgh.pa.us> From: Tom Lane 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/83 X-Sequence-Number: 7141 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