Re: autovacuum maintenance_work_mem - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: autovacuum maintenance_work_mem
Date
Msg-id 201011271904.oARJ4hG17626@momjian.us
Whole thread Raw
In response to Re: autovacuum maintenance_work_mem  (Josh Berkus <josh@agliodbs.com>)
List 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@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Amazon now supporting GPU focused EC2 instances
Next
From: Dimitri Fontaine
Date:
Subject: Re: ALTER OBJECT any_name SET SCHEMA name