| 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: | 200309010130.h811UqV24211@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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 | http://candle.pha.pa.us
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-09-01 01:51:02 | Re: pg_dump bug? |
| Previous Message | Bruce Momjian | 2003-09-01 01:29:40 | Re: FE/BE Protocol - Specific version |