Re: autovacuum_work_mem - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: autovacuum_work_mem
Date
Msg-id CABUevExc0NL3WkSxJB_oEHQpSdHZ7cYcuFn9iPMq-ZF8_t8qpw@mail.gmail.com
Whole thread Raw
In response to Re: autovacuum_work_mem  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: autovacuum_work_mem  (Stephen Frost <sfrost@snowman.net>)
Re: autovacuum_work_mem  (Peter Geoghegan <pg@heroku.com>)
List pgsql-hackers
On Mon, Oct 21, 2013 at 3:42 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Mon, Oct 21, 2013 at 9:36 AM, Peter Eisentraut <peter_e@gmx.net> wrote:
>> On 10/19/13 8:22 PM, Peter Geoghegan wrote:
>>> I don't think it's a problem that
>>> autovacuum_work_mem is kind of similar to vacuum_mem in name.
>>> maintenance_work_mem was last spelt vacuum_mem about 10 years ago.
>>> Enough time has passed that I think it very unlikely that someone
>>> might conflate the two.
>>
>> What is more confusing, however, is that autovacuum_work_mem looks like
>> it's work_mem as used by autovacuum, where it's really
>> maintenance_work_mem as used by autovacuum.  So maybe it should be
>> called autovacuum_maintenance_work_mem.
>
> I think I prefer autovacuum_work_mem.  I don't think sticking the word
> maintenance in there is really adding much in the way of clarity.

+1. If changing at all, then maybe just "autovacuum_mem"? It's not
like there's a different parameter to control a different kind of
memory in autovac, is there?

-- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: autovacuum_work_mem
Next
From: Andres Freund
Date:
Subject: Re: logical changeset generation v6.4