Re: Overhead for stats_command_string et al, take 2 - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Overhead for stats_command_string et al, take 2
Date
Msg-id 200606261907.k5QJ7Ud17608@momjian.us
Whole thread Raw
In response to Overhead for stats_command_string et al, take 2  (Greg Stark <gsstark@mit.edu>)
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.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@momjian.us EnterpriseDB    http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: "Zeugswetter Andreas DCP SD"
Date:
Subject: Re: vacuum, performance, and MVCC
Next
From: Tom Lane
Date:
Subject: Re: Overhead for stats_command_string et al, take 2