From: Alvaro Herrera <alvherre@commandprompt.com>
To: david@lang.hm
Cc: Andrew Sullivan <ajs@commandprompt.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
Date: Wed, 27 Aug 2008 22:19:52 -0400
Message-ID: <20080828021952.GH4071@alvh.no-ip.org> (raw)
In-Reply-To: <alpine.DEB.1.10.0808271516300.907@asgard.lang.hm>
References: <BAY124-W57D3654AF1159CAF8EAC19F5660@phx.gbl>
<82bpze3ou8.fsf@mid.bfk.de>
<alpine.DEB.1.10.0808271436210.907@asgard.lang.hm>
<20080827221338.GP18946@commandprompt.com>
<alpine.DEB.1.10.0808271516300.907@asgard.lang.hm>
david@lang.hm wrote:
> On Wed, 27 Aug 2008, Andrew Sullivan wrote:
>>> seperate copies for the seperate processes (and if at this time it runs of
>>> of memory it invokes the OOM killer to free some space),
>>
>> . . .it kills processes that are using a lot of memory. Those are not
>> necessarily the processes that are allocating memory they don't need.
>
> the bahavior of the OOM killer has changed over time, so far nobody has
> been able to come up with a 'better' strategy for it to follow.
The problem with OOM killer for Postgres is that it tends to kill the
postmaster. That's really dangerous. If it simply killed a backend
then it wouldn't be so much of a problem.
Some time ago I found that it was possible to fiddle with a /proc entry
to convince the OOM to not touch the postmaster. A postmaster with the
raw IO capability bit set would be skipped by the OOM too killer (this
is an Oracle tweak AFAIK).
These are tricks that people could use in their init scripts to protect
themselves.
(I wonder if the initscript supplied by the RPMs or Debian should
contain such a hack.)
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: alvherre@commandprompt.com, david@lang.hm, ajs@commandprompt.com
Subject: Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
In-Reply-To: <20080828021952.GH4071@alvh.no-ip.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox