Re: fsutil ideas

From: Rod Taylor <pg(at)rbt(dot)ca>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-hackers(at)postgresql(dot)org, Neil Conway <neilc(at)samurai(dot)com>, Peter Brant <Peter(dot)Brant(at)wicourts(dot)gov>
Subject: Re: fsutil ideas
Date: 2006-02-24 18:12:54
Message-ID: 1140804774.5092.151.camel@home
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 2006-02-24 at 12:48 -0500, Tom Lane wrote:
> Rod Taylor <pg(at)rbt(dot)ca> 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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Csaba Nagy 2006-02-24 18:20:30 Re: fsutil ideas
Previous Message Tom Lane 2006-02-24 17:48:34 Re: fsutil ideas