From: Tobias Brox <tobias@nordicbet.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Tobias Brox <tobias@nordicbet.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: long running transactions
Date: Tue, 10 Oct 2006 18:39:13 +0200
Message-ID: <20061010163913.GA8097@oppetid.no> (raw)
In-Reply-To: <25404.1160497420@sss.pgh.pa.us>
References: <20061010161027.GA18908@oppetid.no>
<25404.1160497420@sss.pgh.pa.us>
[Tom Lane - Tue at 12:23:40PM -0400]
> Look in pg_locks to see the lowest-numbered transaction ID --- each
> transaction will be holding exclusive lock on its own XID. You can
> correlate that back to pg_stat_activity via the PID.
Thanks a lot for the quick reply - I've already identified one
long-running transaction.
(I'm not allowed to order by xid, and not allowed to cast it to
anything, how come?)
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-performance@postgresql.org
Cc: tobias@nordicbet.com, tgl@sss.pgh.pa.us
Subject: Re: long running transactions
In-Reply-To: <20061010163913.GA8097@oppetid.no>
* 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