Re: procpid?

Greg Smith wrote:
> -It is still useful to set current_query to descriptive text in the
> cases where the transaction is <IDLE> etc. That text is not ambiguous
> with a real query, it is useful for a human-readable view, and it
> improves the potential for pg_stat_sessions to fully replace a
> deprecated pg_stat_activity (instead of just co-existing with it). That
> the query text is overloaded with this information seems agreed to be a
> good thing; it's just that filtering on the state information there
> should not require parsing it. The additional booleans will handle
> that. If idle sessions can be filtered using "WHERE NOT idle", whether
> the current_query for them reads "<IDLE>" or is null won't matter to
> typical monitoring use. Given no strong preference there, using
> "<IDLE>" is both familiar and more human readable.

Uh, if we are going to do that, why not just add the boolean columns to
the existing view? Clearly renaming procpid isn't worth creating
another view.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +