Re: icps, shmmax and shmall - Shared Memory tuning - Mailing list pgsql-general

From Lincoln Yeoh
Subject Re: icps, shmmax and shmall - Shared Memory tuning
Date
Msg-id 5.1.0.14.1.20020429162029.0369abc0@192.228.128.13
Whole thread Raw
In response to Re: icps, shmmax and shmall - Shared Memory tuning  (Martijn van Oosterhout <kleptog@svana.org>)
Responses Re: icps, shmmax and shmall - Shared Memory tuning
List pgsql-general
At 02:52 PM 4/29/02 +1000, Martijn van Oosterhout wrote:
>I'm not saying it's a good idea. Indeed, people saying all the time it's
>bad. But it is the default. If people don't like then they should set the
>over_commit sysctl off (I forget the exact name).

Can't find anything on it on the Linux doc site (tldp). Any links?

Is it better to turn off overcommit and buy more RAM? That way postgresql
or some other process doesn't get killed?

All along I had the impression that Linux had big probs with its VM (since
2.x) with OOM situations (and not so good impressions of the people in
charge of it), and so it's mainly because of overcommit? Ack.

Thanks,
Link.


pgsql-general by date:

Previous
From: Jack Bates
Date:
Subject: CVS tag for 7.2.1?
Next
From: "DB@ ADM"
Date:
Subject: Desc of Functions