Re: IDLE in transaction introspection
Scott Mead <scottm@openscg.com>
From: Scott Mead <scottm@openscg.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Marti Raudsepp <marti@juffo.org>, Albe Laurenz <laurenz.albe@wien.gv.at>, "Andrew Dunstan *EXTERN*" <andrew@dunslane.net>, Simon Riggs <simon@2ndquadrant.com>, Magnus Hagander <magnus@hagander.net>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2011-11-04T18:46:53Z
Lists: pgsql-hackers
On Fri, Nov 4, 2011 at 2:31 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Fri, Nov 4, 2011 at 2:28 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > Robert Haas <robertmhaas@gmail.com> writes:
> >> Maybe there's a better term than "running", like "in progress" or
> >> something of that sort.
> >
> > "active"?
>
> +1.
>
> Letting this one 'poll' a bit more before I post the patch, but here's
what I have:
If waiting == true, then state = WAITING
else
state = appropriate state
I leave the waiting flag in place for posterity. With this in mind, is
the consensus:
RUNNING
or
ACTIVE
--
Scott Mead
OpenSCG http://www.openscg.com
--
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>