From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | David Kerr <dmk(at)mr-paradox(dot)net> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: viewing large queries in pg_stat_activity |
Date: | 2010-02-09 22:39:10 |
Message-ID: | 4B71E40E.4040703@lelarge.info |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Le 09/02/2010 17:05, David Kerr a écrit :
> Magnus Hagander wrote:
>> 2010/2/9 David Kerr <dmk(at)mr-paradox(dot)net>:
>>> It seems like pg_stat_activity truncates the current_query to about
>>> 1024 characters.
>>>
>>> The field is a text, so i'm wondering if there is a way to see the
>>> full query?
>>>
>>> (I know i can turn on log_statement=all, or
>>> log_min_duration_statement) but i'd like
>>> something that doesn't require a restart.
>>
>> The data isn't being tracked, so there is no way to show it. The
>> length of the query tracked can be found in the parameter
>> track_activity_query_size. Note that increasing that will obviously
>> increase the overhead of collecting it.
>>
>>
>
> That's documented in 8.4, does anyone know if it's available in 8.3?
>
No, it's a new feature of 8.4.
--
Guillaume.
http://www.postgresqlfr.org
http://dalibo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Graf | 2010-02-09 23:05:21 | Re: Best way to handle multi-billion row read-only table? |
Previous Message | John R Pierce | 2010-02-09 22:08:09 | Re: Best way to handle multi-billion row read-only table? |