| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Overhead for stats_command_string et al, take 2 |
| Date: | 2006-06-23 00:19:59 |
| Message-ID: | 9220.1151021999@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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.
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2006-06-23 00:40:10 | Re: [CORE] GPL Source and Copyright Questions |
| Previous Message | Tom Lane | 2006-06-23 00:04:04 | Re: [CORE] GPL Source and Copyright Questions |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Glaesemann | 2006-06-23 00:47:13 | Re: Interval aggregate regression failure (expected seems |
| Previous Message | Alvaro Herrera | 2006-06-22 22:18:12 | Re: Overhead for stats_command_string et al, take 2 |