Re: autovacuum maintenance_work_mem

From: Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: autovacuum maintenance_work_mem
Date: 2010-11-16 16:32:28
Message-ID: AANLkTimb4HeaYPS2-CO_Rt_btSY6FiDUHDjRHyXkTfuY@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Nov 17, 2010 at 01:12, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> So for the initial implementation, we could just have each worker set
> its local maintenance_work_mem to autovacuum_maintenance_memory / max_workers.
> That way there's never excessive memory usage.

It sounds reasonable, but is there the same issue for normal connections?
We can limit max connections per user, but there are no quota for total
memory consumed by the user. It might not be an autovacuum-specifix issue.

--
Itagaki Takahiro

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2010-11-16 16:33:22 GiST insert algorithm rewrite
Previous Message Peter Eisentraut 2010-11-16 16:21:48 Re: GCC vs clang