Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: avoiding a problem that postmaster is suddenly killed by OOM-Killer
- From: Jim Nasby <decibel(at)decibel(dot)org>
- To: Toru SHIMOGAKI <shimogaki(dot)toru(at)oss(dot)ntt(dot)co(dot)jp>
- Cc: pgsql-docs(at)postgresql(dot)org
- Subject: Re: avoiding a problem that postmaster is suddenly killed by OOM-Killer
- Date: Mon, 5 Mar 2007 18:38:27 -0600
On Mar 2, 2007, at 6:00 AM, Toru SHIMOGAKI wrote:
I think that to avoid this problem, "increasing swap area" should be added onthis manual. Increasing both physical memory and swap area is easy to understand, but increasing physical memory is not software solution.
Good idea; care to submit a patch? :) -- Jim Nasby jim(at)nasby(dot)net EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
- Follow-Ups:
- Re: avoiding a problem that postmaster is suddenly killed by OOM-Killer
- From: Toru SHIMOGAKI
- Re: avoiding a problem that postmaster is suddenly killed by OOM-Killer
- References:
- avoiding a problem that postmaster is suddenly killed by OOM-Killer
- From: Toru SHIMOGAKI
- avoiding a problem that postmaster is suddenly killed by OOM-Killer
- Prev by Date: avoiding a problem that postmaster is suddenly killed by OOM-Killer
- Next by Date: Re: avoiding a problem that postmaster is suddenly killed by OOM-Killer
- Previous by thread: avoiding a problem that postmaster is suddenly killed by OOM-Killer
- Next by thread: Re: avoiding a problem that postmaster is suddenly killed by OOM-Killer
- Indexes: