From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Stark <greg(dot)stark(at)enterprisedb(dot)com>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: maintenance memory vs autovac |
Date: | 2008-12-03 09:49:13 |
Message-ID: | 49365619.5040207@hagander.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Guillaume Smet wrote:
> On Wed, Dec 3, 2008 at 2:00 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> It seems like mostly a confusion-generator to me. Is there any actual
>> evidence that autovac should use a different maintenance_work_mem than
>> other processes?
>
> IMHO, the point is that we were used to consider the
> maintenance_work_mem as a "one process at a time" thing. Even if it's
> not really true, we usually didn't do maintenance task on a concurrent
> basis.
> The autovacuum workers change that and make it a default behaviour (as
> we can have 3*maintenance_work_mem by default).
It's still one per process, it's just that autovac uses more than one
process. It's probably worthwhile to add a note about the effects of
autovacuum around the documentation of maintenance_work_mem, though.
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2008-12-03 09:49:32 | Re: Erroring out on parser conflicts |
Previous Message | Magnus Hagander | 2008-12-03 09:47:26 | Re: maintenance memory vs autovac |