Re: stats_block_level - Mailing list pgsql-hackers

From Tom Lane
Subject Re: stats_block_level
Date
Msg-id 26650.1185902249@sss.pgh.pa.us
Whole thread Raw
In response to Re: stats_block_level  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: stats_block_level  (Alvaro Herrera <alvherre@commandprompt.com>)
Re: stats_block_level  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
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...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Machine available for community use
Next
From: Tom Lane
Date:
Subject: Re: [PATCHES] allow CSV quote in NULL