Re: Postgres server crash

Ben Chobot <bench@silentmedia.com>

From: Ben <bench@silentmedia.com>
To: "Craig A. James" <cjames@modgraph-usa.com>
Cc: Richard Huxton <dev@archonet.com>, Russell Smith <mr-russ@pws.com.au>, pgsql-performance@postgresql.org
Date: 2006-11-16T21:00:23Z
Lists: pgsql-performance
OOM stands for "Out Of Memory" and it does indeed seem to be the same as 
what IRIX had. I believe you can turn the feature off and also configure 
its overcomitment by setting something in /proc/..... and unfortunately, I 
don't remember more than that.

On Thu, 16 Nov 2006, Craig A. James wrote:

> OOM?  Can you give me a quick pointer to what this acronym stands for and how 
> I can reconfigure it?  It sounds like a "feature" old UNIX systems like SGI 
> IRIX had, where the system would allocate virtual memory that it didn't 
> really have, then kill your process if you tried to use it.  I.e. malloc() 
> would never return NULL even if swap space was over allocated.  Is this what 
> you're talking about?  Having this enabled on a server is deadly for 
> reliability.
>
> Thanks,
> Craig
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>      choose an index scan if your joining column's datatypes do not
>      match
>