Re: autovacuum maintenance_work_mem

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: autovacuum maintenance_work_mem
Date: 2010-11-27 19:04:43
Message-ID: 201011271904.oARJ4hG17626@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Josh Berkus wrote:
>
> > I think the difficulty is figuring out what to get the existing
> > workers to give us some memory when a new one comes along. You want
> > the first worker to potentially use ALL the memory... until worker #2
> > arrives.
>
> Yeah, doing this would mean that you couldn't give worker #1 all the
> memory, because on most OSes it can't release the memory even if it
> wants to.

FYI, what normally happens in this case is that the memory is pushed to
swap by the kernel and never paged in from swap.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dimitri Fontaine 2010-11-27 19:17:48 Re: ALTER OBJECT any_name SET SCHEMA name
Previous Message Bruce Momjian 2010-11-27 18:45:13 Re: pgsql: Remove outdated comments from the regression test files.