Re: Finding if old transactions are running... - Mailing list pgsql-hackers

From jtv@xs4all.nl
Subject Re: Finding if old transactions are running...
Date
Msg-id 18646.202.47.227.16.1109316244.squirrel@202.47.227.16
Whole thread Raw
In response to Re: Finding if old transactions are running...  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> jtv@xs4all.nl writes:

> pg_locks certainly seems like a better solution.  Perhaps it didn't
> exist when you went with pg_stat_activity?  Can't recall offhand.

Neither do I...  But I do need something that will work with at least any
recent backend version--say, 7.2 or since.  The more the better, really. 
Any idea how old pg_locks is?


> Note that you still want to look for your old backend's PID; it seems
> impractically expensive to keep track of the current transaction's XID.
> (At a minimum that would cost another query per xact...)

Yes, I see now--I thought I had the transaction ID handy already anyway,
but I didn't.  Thanks.


Jeroen




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32
Next
From: "John Hansen"
Date:
Subject: Re: [pgsql-hackers-win32] UNICODE/UTF-8 on win32