Re: Determine current running query,

From: Adam Witney <awitney(at)sghms(dot)ac(dot)uk>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Determine current running query,
Date: 2005-03-29 15:50:27
Message-ID: BE6F37D3.4358F%awitney@sghms.ac.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On 29/3/05 4:27 pm, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Adam Witney <awitney(at)sghms(dot)ac(dot)uk> 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.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2005-03-29 16:02:14 Re: Determine current running query, but no query in pg_stat_activity
Previous Message Tom Lane 2005-03-29 15:27:03 Re: Determine current running query, but no query in pg_stat_activity