X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id AEE58D1B16A for ; Mon, 26 Jul 2004 13:43:07 -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 85637-09 for ; Mon, 26 Jul 2004 16:43:02 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id B3BAED1B53F for ; Mon, 26 Jul 2004 13:42:58 -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 i6QGgwTr028912; Mon, 26 Jul 2004 12:42:58 -0400 (EDT) To: schen@graciousstyle.com Cc: pgsql-general@postgresql.org Subject: Re: [ADMIN] how to find transaction associated with a lock In-reply-to: <4105336E.4030604@graciousstyle.com> References: <41001296.3090609@graciousstyle.com> <12341.1090529103@sss.pgh.pa.us> <4100353D.9080202@graciousstyle.com> <13323.1090535841@sss.pgh.pa.us> <4105336E.4030604@graciousstyle.com> Comments: In-reply-to Si Chen message dated "Mon, 26 Jul 2004 09:38:06 -0700" Date: Mon, 26 Jul 2004 12:42:57 -0400 Message-ID: <28911.1090860177@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: 200407/747 X-Sequence-Number: 63346 Si Chen writes: > Thanks for your help last week. I had the problem again where things > got hung up during a transaction, and it was at the order_header table. > Here is what the pg_locks show. Does it confirm what you are saying, > which is that multiple transactions have tried to insert into this table? It's impossible to tell much of anything from a partial view of the pg_locks table. You didn't show us the "granted" flag, so we can't tell which rows represent held locks and which represent waited-for locks; and you didn't show transaction locks at all, which are probably where the issue really is anyway. regards, tom lane