On Fri, 2006-02-24 at 12:48 -0500, Tom Lane wrote: > Rod Taylor <[EMAIL PROTECTED]> writes: > > I watch for table bloat but I haven't figured out a nice way of tracking > > down the postgresql process with the oldest transaction running short of > > patching PostgreSQL to report the XID for a connection in > > pg_stat_activity. > > I don't think you need a patch --- try joining with pg_locks.
Ugh.. pg_locks is the first think I look at to see if something is blocked that shouldn't be. Don't know why I didn't think of using it for the XID value. Thanks. ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
