One of the functions of the DBA is to monitor what people are doing to the database. My experience is that "ps" is often sorely lacking in this regard: its output is somewhat limited, from what I've seen, and in any case the DBA's domain is the database itself: that's the environment he's going to be most proficient in.
The ability to select the list of current connections from pg_stat_activity is really handy for monitoring the database, but the default configuration disables stats_command_string -- so the current_query winds up being blank by default. That's not exactly the most useful configuration for the DBA. Would it make more sense to enable stats_command_string by default? It could be a problem if doing so would have a significant impact on performance, but that's the only reason I can think of for not doing it. Are there others? It would also be handy if users could see their own queries while the rest remain blank. That would require changing pg_stat_get_backend_activity() so that it returns a value if the user is the superuser or if the user asking for the answer is the same as the user who owns the backend entry being looked up. Are there any pitfalls to implementing that? -- Kevin Brown [EMAIL PROTECTED] ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]