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

From Simon Riggs
Subject Re: IDLE in transaction introspection
Date
Msg-id CA+U5nML4W=SsfEzVSNhYUk0=Ak48uynCQ-2_y6jg2eeJd3RN7Q@mail.gmail.com
Whole thread Raw
In response to Re: IDLE in transaction introspection  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On Tue, Nov 1, 2011 at 12:41 PM, Magnus Hagander <magnus@hagander.net> wrote:
> On Tue, Nov 1, 2011 at 13:19, Simon Riggs <simon@2ndquadrant.com> wrote:
>> 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.
>
> That would be the backwards compatible way I suggested.

Sorry Magnus, I hadn't read the whole thread.

+1 to your suggestion.

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


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: IDLE in transaction introspection
Next
From: Merlin Moncure
Date:
Subject: Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."?