Re: display previous query string of idle-in-transaction

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Robert Haas" <robertmhaas(at)gmail(dot)com>,"daveg" <daveg(at)sonic(dot)net>
Cc: "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "decibel" <decibel(at)decibel(dot)org>, "Greg Stark" <stark(at)enterprisedb(dot)com>, "Asko Oja" <ascoja(at)gmail(dot)com>, "Tatsuhito Kasahara" <kasahara(dot)tatsuhito(at)oss(dot)ntt(dot)co(dot)jp>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: display previous query string of idle-in-transaction
Date: 2009-07-24 14:47:06
Message-ID: 4A69831A0200002500028D0D@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

daveg <daveg(at)sonic(dot)net> wrote:
> On Thu, Jun 04, 2009 at 10:22:41PM -0400, Robert Haas wrote:

>> 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).

+1

> I like this idea a lot. Possibly it would be useful to have the end
> time of the last query too, then one could find idle sessions that
> were old and truly idle rather than just waiting for a busy client
> to send the next query.
>
> select ... from pg_stat_activity
> where idle
> and last_statement_endtime < now() - interval '1 minute';

+1

Of course, you might be more interested in those which are idle in a
transaction, but that's easily done with these changes -- just throw
in xact_start IS NULL.

-Kevin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-07-24 14:58:15 Re: display previous query string of idle-in-transaction
Previous Message Andrew Dunstan 2009-07-24 14:27:54 Re: join regression failure on cygwin