Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Overhead for stats_command_string et al, take 2
- 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: Mon, 26 Jun 2006 15:07:30 -0400 (EDT)
- Message-id: <200606261907(dot)k5QJ7Ud17608(at)momjian(dot)us>
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. +
- Follow-Ups:
- Re: Overhead for stats_command_string et al, take 2
- From: Tom Lane
- Re: Overhead for stats_command_string et al, take 2
- References:
- Re: Overhead for stats_command_string et al, take 2
- From: Tom Lane
- Re: Overhead for stats_command_string et al, take 2
- Prev by Date: Re: Overhead for stats_command_string et al, take 2
- Next by Date: Re: Overhead for stats_command_string et al, take 2
- Previous by thread: Re: Overhead for stats_command_string et al, take 2
- Next by thread: Re: Overhead for stats_command_string et al, take 2
- Indexes: