On Thu, Jun 4, 2009 at 9:54 PM, Tatsuhito Kasahara<kasahara.tatsuh...@oss.ntt.co.jp> wrote: > Kevin Grittner wrote: >> >> Greg Stark <st...@enterprisedb.com> wrote: >>> >>> Should this patch be on the commitfest page for 8.5? Or is there a >>> consensus already that it's a bad idea? >>> >>> Personally I actually think this makes a lot of sense to do. >> >> +1 >> It at least gives one a reasonable chance to get a useful clue.... > > +1 > # And I'm going to register this patch on the next commitfest page.
I don't actually remember seeing actual code to implement this - is this a patch, or just an idea? (I guess if this gets added to the CommitFest page there will be a pointer to the code, but somehow I can't find it at the moment.) The only thing I don't like about this is that I think it's kind of a hack to shove the <IDLE> in transaction designation and the query string into the same database column. I've never liked having to write: select sum(1) from pg_stat_activity where current_query = '<IDLE> in transaction'; ...and I like it even less if I now have to modify that query to use "like". We should find some way to represent this as structured data... maybe make a separate column called "idle" that's a boolean, or something, and let the query column contain the most recent query (whether or not it's still executing). ...Robert -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
