| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: Overhead for stats_command_string et al, take 2 |
| Date: | 2006-06-26 19:07:30 |
| Message-ID: | 200606261907.k5QJ7Ud17608@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Yep, I see 8% here. I will add a patch to allow the ps display to be
> > turned off.
>
> I think we'd still want a backend to set the PS display once with its
> identification data (user/DB name and client address). It's just the
> transient activity updates that should stop.
Oh, good point. Do we remove stats_command_string? Does it have any
measurable overhead? I see a little here, like 1%.
--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-06-26 19:10:03 | Re: Overhead for stats_command_string et al, take 2 |
| Previous Message | Tom Lane | 2006-06-26 18:54:56 | Re: Overhead for stats_command_string et al, take 2 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-06-26 19:10:03 | Re: Overhead for stats_command_string et al, take 2 |
| Previous Message | Tom Lane | 2006-06-26 18:54:56 | Re: Overhead for stats_command_string et al, take 2 |