Re: IDLE in transaction introspection
Scott Mead <scottm@openscg.com>
From: Scott Mead <scottm@openscg.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruce Momjian <bruce@momjian.us>, Albe Laurenz <laurenz.albe@wien.gv.at>, "Andrew Dunstan *EXTERN*" <andrew@dunslane.net>, Simon Riggs <simon@2ndquadrant.com>, Robert Haas <robertmhaas@gmail.com>, Magnus Hagander <magnus@hagander.net>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2011-11-15T14:44:06Z
Lists: pgsql-hackers
Attachments
- pg_stat_activity_state_query.v2.patch (application/octet-stream) patch v2
On Thu, Nov 10, 2011 at 2:49 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Bruce Momjian <bruce@momjian.us> writes: > > Well, we could use an optional "details" string for that. If not, we > > are still using the magic-string approach, which I thought we didn't > > like. > > No, we're not using magic strings, we're using an enum --- maybe not an > officially declared enum type, but it's a column with a predetermined > set of possible values. It would be a magic string if it were still in > the "query" field and thus confusable with user-written queries. > Fell off the map last week, here's v2 that: * RUNNING => active * all states from CAPS to lower case -- Scott Mead OpenSCG http://www.openscg.com > > regards, tom lane >