Re: maintenance memory vs autovac - Mailing list pgsql-hackers

From Guillaume Smet
Subject Re: maintenance memory vs autovac
Date
Msg-id 1d4e0c10812022306w59e3f1e8ud5aa53ffe33f5b46@mail.gmail.com
Whole thread Raw
In response to Re: maintenance memory vs autovac  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: maintenance memory vs autovac  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On Wed, Dec 3, 2008 at 2:00 AM, Tom Lane <tgl@sss.pgh.pa.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).

From my point of view, the best solution would be to share the
maintenance_work_mem amongst all the workers but I suppose it's not
technically possible.

-- 
Guillaume


pgsql-hackers by date:

Previous
From: "Pavan Deolasee"
Date:
Subject: Re: Hot Standby (commit fest version - v5)
Next
From: "Fujii Masao"
Date:
Subject: Re: Sync Rep: First Thoughts on Code