Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 4466C9F99DA for ; Thu, 13 Sep 2007 10:58:17 -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 90985-02 for ; Thu, 13 Sep 2007 10:58:08 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 958729F994E for ; Thu, 13 Sep 2007 10:58:13 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l8DDwCPY008030; Thu, 13 Sep 2007 09:58:12 -0400 (EDT) To: Tino Schwarze cc: pgsql-admin@postgresql.org Subject: Re: automatically detecting long timed locks In-reply-to: <20070913091221.GC6423@easy2.in-chemnitz.de> References: <20070912204657.GC29139@easy2.in-chemnitz.de> <20070913091221.GC6423@easy2.in-chemnitz.de> Comments: In-reply-to Tino Schwarze message dated "Thu, 13 Sep 2007 11:12:21 +0200" Date: Thu, 13 Sep 2007 09:58:12 -0400 Message-ID: <8029.1189691892@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200709/90 X-Sequence-Number: 26851 Tino Schwarze writes: > So I'd like to watch for transactions waiting for the lock in step 3 - I > do not care for the time it took to perform the work. Dunno if this is of any use to you, but there is a "log_lock_waits" feature in CVS HEAD that seems to be exactly what you want. I couldn't recommend running 8.3 in production yet, but it wouldn't be out of the realm of reason to back-port the patch for that. regards, tom lane