public inbox for [email protected]
help / color / mirror / Atom feedavoiding a problem that postmaster is suddenly killed by OOM-Killer
3+ messages / 2 participants
[nested] [flat]
* avoiding a problem that postmaster is suddenly killed by OOM-Killer
@ 2007-03-02 12:00 Toru SHIMOGAKI <[email protected]>
2007-03-06 00:38 ` Re: avoiding a problem that postmaster is suddenly killed by OOM-Killer Jim Nasby <[email protected]>
0 siblings, 1 reply; 3+ messages in thread
From: Toru SHIMOGAKI @ 2007-03-02 12:00 UTC (permalink / raw)
To: pgsql-docs
Hello all,
To avoid a problem that postmaster is suddenly killed by OOM-Killer, some
techniques are described in "16.4.3. Linux Memory Overcommit"
http://www.postgresql.org/docs/8.2/interactive/kernel-resources.html#AEN19362
One way to avoid this problem is to run PostgreSQL on a machine where you can
be sure that other processes will not run the machine out of memory.
On Linux 2.6 and later, a better solution is to modify the kernel's behavior
so that it will not "overcommit" memory. This is done by selecting strict
overcommit mode via sysctl:
This description may be misread, at least to me, because OOM-Killer's behavor
has nothing to do with overcommit mode. It is true that turning overcommit off
is one of the solutions but it is not enough: OOM-Killer is invoked whenever
physical memory is exhausted not only by user application but also by in-kernel
working. I checked it with some kernel hackers on Linux-2.6.9-42 (RHEL4 Update4).
I think that to avoid this problem, "increasing swap area" should be added on
this manual. Increasing both physical memory and swap area is easy to
understand, but increasing physical memory is not software solution.
Best regards,
--
Toru SHIMOGAKI<[email protected]>
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: avoiding a problem that postmaster is suddenly killed by OOM-Killer
2007-03-02 12:00 avoiding a problem that postmaster is suddenly killed by OOM-Killer Toru SHIMOGAKI <[email protected]>
@ 2007-03-06 00:38 ` Jim Nasby <[email protected]>
2007-03-06 06:58 ` Re: avoiding a problem that postmaster is suddenly killed by OOM-Killer Toru SHIMOGAKI <[email protected]>
0 siblings, 1 reply; 3+ messages in thread
From: Jim Nasby @ 2007-03-06 00:38 UTC (permalink / raw)
To: Toru SHIMOGAKI <[email protected]>; +Cc: pgsql-docs
On Mar 2, 2007, at 6:00 AM, Toru SHIMOGAKI wrote:
> I think that to avoid this problem, "increasing swap area" should
> be added on
> this 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 [email protected]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: avoiding a problem that postmaster is suddenly killed by OOM-Killer
2007-03-02 12:00 avoiding a problem that postmaster is suddenly killed by OOM-Killer Toru SHIMOGAKI <[email protected]>
2007-03-06 00:38 ` Re: avoiding a problem that postmaster is suddenly killed by OOM-Killer Jim Nasby <[email protected]>
@ 2007-03-06 06:58 ` Toru SHIMOGAKI <[email protected]>
0 siblings, 0 replies; 3+ messages in thread
From: Toru SHIMOGAKI @ 2007-03-06 06:58 UTC (permalink / raw)
To: Jim Nasby <[email protected]>; +Cc: pgsql-docs
Jim Nasby wrote:
> On Mar 2, 2007, at 6:00 AM, Toru SHIMOGAKI wrote:
>> I think that to avoid this problem, "increasing swap area" should be
>> added on
>> this 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? :)
Yes, I'll submit a patch as soon as possible.
--
Toru SHIMOGAKI<[email protected]>
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2007-03-06 06:58 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2007-03-02 12:00 avoiding a problem that postmaster is suddenly killed by OOM-Killer Toru SHIMOGAKI <[email protected]>
2007-03-06 00:38 ` Jim Nasby <[email protected]>
2007-03-06 06:58 ` Toru SHIMOGAKI <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox