From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tino Schwarze <postgresql@tisc.de>
Cc: pgsql-admin@postgresql.org
Subject: Re: automatically detecting long timed locks
Date: Thu, 13 Sep 2007 09:58:12 -0400
Message-ID: <8029.1189691892@sss.pgh.pa.us> (raw)
In-Reply-To: <20070913091221.GC6423@easy2.in-chemnitz.de>
References: <20070912204657.GC29139@easy2.in-chemnitz.de>
<dcc563d10709121502o50221f23m4cd1b420b649b429@mail.gmail.com>
<20070913091221.GC6423@easy2.in-chemnitz.de>
Tino Schwarze <postgresql@tisc.de> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, postgresql@tisc.de
Subject: Re: automatically detecting long timed locks
In-Reply-To: <8029.1189691892@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox