From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Remove vacuum_defer_cleanup_age |
Date: | 2016-10-18 20:18:07 |
Message-ID: | 6907f5e0-19de-2aac-ac70-68a56ae781f4@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10/12/2016 05:00 PM, Robert Haas wrote:
> On Sun, Oct 9, 2016 at 9:51 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>> Given that hot_standby_feedback is pretty bulletproof now, and a lot of
>> the work in reducing replay conflicts, I think the utility of
>> vacuum_defer_cleanup_age is at an end. I really meant so submit a patch
>> to remove it to 9.6, but it got away from me.
>>
>> Any objections to removing the option in 10?
>
> I'm not sure I see the point.
Redusing the number of configuration variables is an a-priori good. In
aggregate, the more knobs we have, the harder it is to learn how to
admin Postgres. Therefore any time a config variable becomes obsolete,
we should remove it.
--
--
Josh Berkus
Red Hat OSAS
(any opinions are my own)
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2016-10-18 20:25:51 | Re: PATCH: two slab-like memory allocators |
Previous Message | Claudio Freire | 2016-10-18 20:04:32 | Re: Indirect indexes |