From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: GUC variable renaming, redux |
Date: | 2007-09-23 19:15:02 |
Message-ID: | 6381.1190574902@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2007-09-23 19:36:29 | Re: [PATCHES] Eliminate more detoast copies for packed varlenas |
Previous Message | Peter Eisentraut | 2007-09-23 19:04:42 | Re: GUC variable renaming, redux |