Re: GUC variable renaming, redux - Mailing list pgsql-hackers

From Tom Lane
Subject Re: GUC variable renaming, redux
Date
Msg-id 6381.1190574902@sss.pgh.pa.us
Whole thread Raw
In response to Re: GUC variable renaming, redux  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Tom Lane wrote:
>> Actually ... does stats_reset_on_server_start have a reason to live
>> at all?

> We also have a stats reset after recovery, and a function to reset it at
> the user's whim, so I agree that there doesn't seem to be any reason to
> keep it.  Neither of these existed when stats_reset_on_server_start was
> implemented, IIRC.

Good point about the function --- that seems more than sufficient for
any possible usefulness of a reset behavior.

So if stats_reset_on_server_start goes away, then we have only two
variable names to worry about, and they control separate behaviors
so there seems no compelling reason to name them alike.  That leaves
me favoring the approach of calling them
    track_activities    track_counts

Rather than calling for more discussion, maybe I should just say
"has anyone got a strong objection to these names"?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: GUC variable renaming, redux
Next
From: Gregory Stark
Date:
Subject: Re: [PATCHES] Eliminate more detoast copies for packed varlenas