From: | Ben <bench(at)silentmedia(dot)com> |
---|---|
To: | "Craig A(dot) James" <cjames(at)modgraph-usa(dot)com> |
Cc: | Richard Huxton <dev(at)archonet(dot)com>, Russell Smith <mr-russ(at)pws(dot)com(dot)au>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Postgres server crash |
Date: | 2006-11-16 21:00:23 |
Message-ID: | Pine.LNX.4.64.0611161246070.8155@GRD.cube42.tai.silentmedia.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2006-11-16 21:01:28 | Re: Context switch storm |
Previous Message | Richard Huxton | 2006-11-16 18:22:10 | Re: Postgres server crash |