From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Frank Joerdens <frank(at)joerdens(dot)de> |
Cc: | pgsql-general(at)postgresql(dot)org, dev <dev(at)woome(dot)com> |
Subject: | Re: reason for default PGSTAT_ACTIVITY_SIZE |
Date: | 2010-01-05 20:00:34 |
Message-ID: | 4B439A62.8080405@lelarge.info |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Le 05/01/2010 20:36, Frank Joerdens a écrit :
> On Tue, Jan 5, 2010 at 6:24 PM, Guillaume Lelarge
> <guillaume(at)lelarge(dot)info> wrote:
> [...]
>>> Is there a good reason to set PGSTAT_ACTIVITY_SIZE at 256 and is my
>>> only option to recompile the server? Is there a practical
>>> limit/drawback to making the variable say 4 or 8 times the default?
> [...]
>> On current releases, it has a higher value (1024 IIRC). And it's a
>> configuration parameter on 8.4.
>
> A cool that's great news! We'll probably deal with this issue then by
> going from 8.3->8.4 asap.
>
> But I just grepped the 8.3 source tree for PGSTAT_ACTIVITY_SIZE and
> it's not there? So the value/variable has a different name now?
>
PGBE_ACTIVITY_SIZE since 8.2.
In 8.4, the GUC is named track_activity_query_size.
--
Guillaume.
http://www.postgresqlfr.org
http://dalibo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Milan Zamazal | 2010-01-05 20:05:48 | Re: Large tables, ORDER BY and sequence/index scans |
Previous Message | Antonio Goméz Soto | 2010-01-05 19:56:32 | Re: Using table name in column for joining |