Re: IDLE in transaction introspection - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: IDLE in transaction introspection
Date
Msg-id CA+U5nMJc5jkFp3b6MA2hUHbg-D5Lmd3PTE-fc-8NWzYK0_g5GA@mail.gmail.com
Whole thread Raw
In response to Re: IDLE in transaction introspection  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: IDLE in transaction introspection
Re: IDLE in transaction introspection
List pgsql-hackers
On Mon, Oct 31, 2011 at 10:13 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Mon, Oct 31, 2011 at 5:45 PM, Magnus Hagander <magnus@hagander.net> wrote:
>> Actually, for the future, it might be useful to have a "state" column,
>> that holds the idle/in transaction/running status, instead of the
>> tools having to parse the query text to get that information...
>
> +1 for doing it this way.  Splitting "current_query" into "query" and
> "state" would be more elegant and easier to use all around.

Why not leave it exactly as it is, and add a previous_query column?

That gives you exactly what you need without breaking anything.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: unite recovery.conf and postgresql.conf
Next
From: Magnus Hagander
Date:
Subject: Re: IDLE in transaction introspection