From db5d7ccac99e4b1f3ea0d09f7fc1b6f0682f336d Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Thu, 20 Mar 2003 18:51:16 +0000 Subject: It would also be handy if users could see their own pg_stat_activity queries while the rest remain blank. Kevin Brown --- doc/src/sgml/monitoring.sgml | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml index 002134c9acd..48bbe9561bb 100644 --- a/doc/src/sgml/monitoring.sgml +++ b/doc/src/sgml/monitoring.sgml @@ -1,5 +1,5 @@ @@ -212,9 +212,10 @@ postgres: user database host STATS_COMMAND_STRING configuration option has been enabled. Furthermore, these columns can only be accessed by - superusers; to other users, they always appear NULL. (Note that - because of the collector's reporting delay, current query will - only be up-to-date for long-running queries.) + superusers; or when the user examining the view is the same as the user + in the row; for others it reads as null. (Note that because of the + collector's reporting delay, current query will only be up-to-date for + long-running queries.) @@ -534,7 +535,8 @@ postgres: user database host text Current query of backend process (NULL if caller is not - superuser, or STATS_COMMAND_STRING is not enabled) + superuser, or is the same user as that of the backend being queried, + or STATS_COMMAND_STRING is not enabled) -- cgit v1.2.3