Re: maintenance memory vs autovac

From: Greg Stark <greg(dot)stark(at)enterprisedb(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: maintenance memory vs autovac
Date: 2008-12-02 14:39:03
Message-ID: 834BF7B8-A49D-4269-85D3-B48BA666FAE4@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Seems it would make more sense to just divide maintenance_work_mem by
the number of workers for autovacuum.

This sounds familiar. Didn't we already decide to do this once?

One concern I have about this is people asking "how come when I
runvacuum manually it takes x minutes but when autovacuum runs it it
tale 5x minutes?"

greg

On 2 Dec 2008, at 01:38 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:

> Would it make sense to be able to configure maintenance_work_mem
> specifically for the autovacuum processes? Given that there can be a
> number of them, it might be good to be able to have one default for
> all
> *other* processes, and a separate one from the ones kicked off by
> autovac?
>
> //Magnus
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2008-12-02 14:54:30 Re: maintenance memory vs autovac
Previous Message Heikki Linnakangas 2008-12-02 14:21:09 Re: PiTR and other architectures....