From: | Jon Lapham <lapham(at)extracta(dot)com(dot)br> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Pre-allocation of shared memory ... |
Date: | 2003-06-12 14:52:46 |
Message-ID: | 3EE893BE.7080305@extracta.com.br |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> [snip]
> The
> setting now called "paranoid overcommit" is IMHO the *only* acceptable
> one for any sort of server system. With anything else, you risk having
> critical userspace daemons killed through no fault of their own.
Wow. Thanks for the info. I found the documentation you are referring
to in Documentation/vm/overcommit-accounting (on a stock RH9 machine).
It seems that the overcommit policy is set via the sysctl
`vm.overcommit_memory'. So...
[root(at)bilbo src]# sysctl -a | grep -i overcommit
vm.overcommit_memory = 0
...the default seems to be "Heuristic overcommit handling". It seems
that what we want is "vm.overcommit_memory = 3" for paranoid overcommit.
Thanks for getting to the bottom of this Tom. It *is* insane that the
default isn't "paranoid overcommit".
--
-**-*-*---*-*---*-*---*-----*-*-----*---*-*---*-----*-----*-*-----*---
Jon Lapham <lapham(at)extracta(dot)com(dot)br> Rio de Janeiro, Brasil
Work: Extracta Moléculas Naturais SA http://www.extracta.com.br/
Web: http://www.jandr.org/
***-*--*----*-------*------------*--------------------*---------------
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-06-12 15:05:12 | Re: Pre-allocation of shared memory ... |
Previous Message | Tom Lane | 2003-06-12 14:29:31 | Re: Pre-allocation of shared memory ... |