On 29/3/05 4:27 pm, "Tom Lane" <[EMAIL PROTECTED]> wrote: > Adam Witney <[EMAIL PROTECTED]> writes: >> Shouldn't there be something in current_query? > > Only if (a) you have stats_command_string turned on, *and* (b) you > are a superuser or the owner of the target process.
I am logged in as the superuser, and I just switched stats_command_string on. Table now looks like this bugasbase=# SELECT * from pg_stat_activity ; datid | datname | procpid | usesysid | usename | current_query | query_start ----------+-----------+---------+----------+---------+---------------+------ -------------------------- 80573819 | bugasbase | 23197 | 1 | pgsql | <IDLE> | 29/03/2005 17:03:25.911288 BST 80573819 | bugasbase | 23195 | 109 | lubrook | | I did find a reference on google to the fact that there was/is a max query size length for this? I think this was for 7.3.5, is this still the case? Maybe this is the reason it is not showing up (it is quite a large query string)? Thanks Adam -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
