Le 05/01/2010 20:36, Frank Joerdens a écrit :
> On Tue, Jan 5, 2010 at 6:24 PM, Guillaume Lelarge
> 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 o
On Tue, Jan 5, 2010 at 6:24 PM, Guillaume Lelarge
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
Le 05/01/2010 18:02, frank joerdens a écrit :
> From my angle, it looks as if the default for PGSTAT_ACTIVITY_SIZE is
> too small, or rather that it ought to be configurable at least, so
> that longer current_query strings that are shown via
> pg_stat_get_backend_activity() in the system view pg_st
