Default value for stats_command_string (GUC)

Started by David Fetterover 21 years ago2 messageshackers
Jump to latest
#1David Fetter
david@fetter.org

Kind people,

I'm writing up a pg_top. The first cut will be for 8.0, as it relies
on (I know, I know) set-returning functions in plperlu. To make it do
the right thing, stats_command_string needs to be on.

Is there some large impact of setting this to be on by default? If
not, could we set that as the default setting?

Looking forward to a lively discussion on this,
I remain,
Yr. obd't ser't,
D
--
David Fetter david@fetter.org http://fetter.org/
phone: +1 510 893 6100 mobile: +1 415 235 3778

Remember to vote!

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: David Fetter (#1)
Re: Default value for stats_command_string (GUC)

David Fetter <david@fetter.org> writes:

Is there some large impact of setting this to be on by default?

A UDP send() per command, plus the ensuing activity in the pgstats
processes (which are by default activated only by backend start/stop).

If you want it to be on by default, I think the onus is on you to prove
that it's *not* significant, not vice versa.

regards, tom lane