| From: | Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Scott Mead <scottm(at)openscg(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: IDLE in transaction introspection |
| Date: | 2011-10-31 21:59:34 |
| Message-ID: | CAJKUy5gmS1tA=UP6jJkMfp8AVOXbJrp-mdf1Mzdeb=24C=kztw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Oct 31, 2011 at 4: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...
>
if we are going to create the "state" column let's do it now and
change current_query for last_query (so last query can be running, or
it was the last before enter in idle state)
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-10-31 22:13:04 | Re: IDLE in transaction introspection |
| Previous Message | Magnus Hagander | 2011-10-31 21:45:42 | Re: IDLE in transaction introspection |