Re: icps, shmmax and shmall - Shared Memory tuning

From: Lincoln Yeoh <lyeoh(at)pop(dot)jaring(dot)my>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: dorian dorian <dorian37076(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: icps, shmmax and shmall - Shared Memory tuning
Date: 2002-04-29 08:38:17
Message-ID: 5.1.0.14.1.20020429162029.0369abc0@192.228.128.13
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Francois Suter 2002-04-29 08:46:49 Re: pid gets overwritten in OSX
Previous Message DB@ ADM 2002-04-29 08:28:12 Desc of Functions