On Jun 16, 2011, at 9:31 AM, Greg Smith wrote: > -A case could be made for making some of these state fields null, instead > true or false, in situations where the session is not visible. If you don't > have rights to see the connection activity, setting idle, idle_transaction, > and active all to null may be the right thing to do. More future > bikeshedding is likely on this part, once an initial patch is ready for > testing. I'd want to get some specific tests against the common monitoring > goals of tools like check_postgres and the Munin plug-in to see which > implementation makes more sense for them as input on that.
ISTM this should be driven by what data we actually expose. If we're willing to expose actual information for idle, idle_transaction and waiting for backends that you don't have permission to see the query for, then we should expose the actual information (I personally think this would be useful). OTOH, if we are not willing to expose that information, then we should certainly set those fields to null instead of some default value. -- Jim C. Nasby, Database Architect j...@nasby.net 512.569.9461 (cell) http://jim.nasby.net -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
