| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| 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 18:14:01 |
| Message-ID: | 19583.1163700841@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
"Craig A. James" <cjames(at)modgraph-usa(dot)com> writes:
> OOM? Can you give me a quick pointer to what this acronym stands for
> and how I can reconfigure it?
See "Linux Memory Overcommit" at
http://www.postgresql.org/docs/8.1/static/kernel-resources.html#AEN18128
or try googling for "OOM kill" for non-Postgres-specific coverage.
> 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.
No kidding :-(. The default behavior in Linux is extremely unfortunate.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Huxton | 2006-11-16 18:22:10 | Re: Postgres server crash |
| Previous Message | Tom Lane | 2006-11-16 18:10:31 | Re: Postgres server crash |