Re: Linux2.6 overcommit behaviour - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Linux2.6 overcommit behaviour
Date
Msg-id 200309010130.h811UqV24211@candle.pha.pa.us
Whole thread Raw
In response to Re: Linux2.6 overcommit behaviour  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Linux2.6 overcommit behaviour
List pgsql-hackers
Andrew Dunstan wrote:
> I believe that the swap slot can be subsequently freed, though. In 
> theory your available virtual memory should be (almost) RAM+swap. In 
> practice, Linux can run too close to that limit, (or way over it if you 
> turn the checks off). But restricting the maximum possible pages to 
> RAM/2 + swap should normally be fine. IANAKH, though.
> 
> Also note that the truly bad thing about the OOM killer is that it can 
> affect a process that is not making any new memory demands at all.

How does the OOM killer kill processes, kill -9 or kill -1 and wait?

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: FE/BE Protocol - Specific version
Next
From: Bruce Momjian
Date:
Subject: Re: pg_dump bug?