Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Seeing stats_command_string with almost zero overhead is great news!
> > Should we remove that setting and just have it enabled all
> > the time?
> If you don't need it, you shouldn't have to pay any overhead for it,
> I think. One could make an argument now for having stats_command_string
> default to ON, though.
The attached patch makes stats_command_string default to 'on', and
updates the documentation.
> Something that might also be interesting is an option to suppress
> per-command ps_status reporting. On machines where updating ps status
> takes a kernel call, there's now a pretty good argument why you might
> want to turn that off and rely on pg_stat_activity instead.
OK, can I get a timing report from someone with the title on/off that
shows a difference?
Bruce Momjian bruce(at)momjian(dot)us
+ If your life is a hard drive, Christ can be your backup. +
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2006-06-26 17:24:41|
|Subject: pgsql: Change the row constructor syntax (ROW(...)) so that list |
|Previous:||From: Stefan Kaltenbrunner||Date: 2006-06-26 17:08:54|
|Subject: GIN index creation extremely slow ?|
pgsql-patches by date
|Next:||From: Tom Lane||Date: 2006-06-26 17:32:04|
|Subject: Re: [HACKERS] Overhead for stats_command_string et al, take 2 |
|Previous:||From: Bruce Momjian||Date: 2006-06-26 16:40:53|
|Subject: Re: Overhead for stats_command_string et al, take 2|