Skip site navigation (1) Skip section navigation (2)

Re: Linux2.6 overcommit behaviour

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Linux2.6 overcommit behaviour
Date: 2003-09-01 01:30:52
Message-ID: (view raw, whole thread or download thread mbox)
Lists: 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                        |
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to


pgsql-hackers by date

Next:From: Bruce MomjianDate: 2003-09-01 01:51:02
Subject: Re: pg_dump bug?
Previous:From: Bruce MomjianDate: 2003-09-01 01:29:40
Subject: Re: FE/BE Protocol - Specific version

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group