| From: | Frank Joerdens <frank(at)joerdens(dot)de> |
|---|---|
| To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
| 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 19:36:26 |
| Message-ID: | 7d10d2df1001051136s65d60a1fl82b0b6e8810271cd@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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?
Cheers,
Frank
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Roman Neuhauser | 2010-01-05 19:52:33 | Re: set-level update fails with unique constraint violation |
| Previous Message | Merlin Moncure | 2010-01-05 18:48:29 | Re: pl/perl not rethrowing pl/pgsql exceptions |