Re: IDLE in transaction introspection

<p><br /> On Nov 5, 2011 9:02 AM, "Greg Smith" <<a href="mailto:greg@2ndquadrant.com">greg@2ndquadrant.com</a>>
wrote:<br/> ><br /> > On 11/04/2011 05:01 PM, Tom Lane wrote:<br /> >><br /> >> Scott Mead<<a
href="mailto:scottm@openscg.com">scottm@openscg.com</a>> writes:<br /> >>   <br /> >>><br />
>>>   I leave the waiting flag in place for posterity.  With this in mind, is<br /> >>> the
consensus:<br/> >>>    RUNNING<br /> >>>     or<br /> >>>    ACTIVE<br /> >>>    
<br/> >><br /> >> Personally, I'd go for lower case.<br /> >>   <br /> ><br /> ><br /> > I
wasthinking it would be nice if this state looked like the WAL sender state values in pg_stat_replication, which are
alllower case.  For comparison those states are:<br /> ><br /> > startup<br /> > backup<br /> > catchup<br
/>> streaming<p> +1, it'll be easier to query against.  <br /> ><br /> > -- <br /> > Greg Smith  
2ndQuadrantUS    greg@2ndQuadrant.com   Baltimore, MD<br /> > PostgreSQL Training, Services, and 24x7 Support  <a
href="http://www.2ndQuadrant.us">www.2ndQuadrant.us</a><br/> ><br /> ><br /> ><br /> > -- <br /> > Sent
viapgsql-hackers mailing list (<a href="mailto:pgsql-hackers@postgresql.org">pgsql-hackers@postgresql.org</a>)<br />
>To make changes to your subscription:<br /> > <a
href="http://www.postgresql.org/mailpref/pgsql-hackers">http://www.postgresql.org/mailpref/pgsql-hackers</a><br/>