| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Scott Mead <scottm(at)openscg(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: IDLE in transaction introspection |
| Date: | 2011-11-01 12:19:39 |
| Message-ID: | CA+U5nMJc5jkFp3b6MA2hUHbg-D5Lmd3PTE-fc-8NWzYK0_g5GA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Oct 31, 2011 at 10:13 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Mon, Oct 31, 2011 at 5:45 PM, Magnus Hagander <magnus(at)hagander(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2011-11-01 12:41:20 | Re: IDLE in transaction introspection |
| Previous Message | Simon Riggs | 2011-11-01 12:14:47 | Re: unite recovery.conf and postgresql.conf |