Re: stats_block_level - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: stats_block_level
Date
Msg-id 20070731180937.GG15602@alvh.no-ip.org
Whole thread Raw
In response to Re: stats_block_level  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: stats_block_level  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: stats_block_level  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Tom Lane wrote:
> Alvaro Herrera <alvherre@commandprompt.com> writes:
> > Simon Riggs wrote:
> >> Methinks it should be: stats_<something>, so that people find it in the
> >> same place as stats_query_string, which is still there.
> 
> > Hum, but the order in postgresql.conf is arbitrary, right?
> 
> I concur with Simon that it should have some relationship to
> stats_query_string.  However, stats_collection doesn't appeal to me
> because that sounds like it would subsume stats_query_string (it seems
> like a master control toggle, as stats_start_collector used to be).
> Maybe something like stats_count_events?
> 
> Or we could get radical and rename both of them...

Well, it is a bit misleading to have the query_string stuff be named
"stats" when it's not actually collected by pgstats at all.  Maybe
rename it to "collect_query_string".  With the other name being
"collect_stats", they would show up together in SHOW ALL.

I am not sure about using plural/singular though: why isn't it
"stats_query_strings" instead?  (We do have "log_connections" etc).

-- 
Alvaro Herrera                  http://www.amazon.com/gp/registry/5ZYLFMCVHXC
"Porque francamente, si para saber manejarse a uno mismo hubiera que
rendir examen... ¿Quién es el machito que tendría carnet?"  (Mafalda)


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: stats_block_level
Next
From: Oleg Bartunov
Date:
Subject: Re: default_text_search_config and expression indexes