pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Greg Smith <gsmith@gregsmith.com>
To: Bill Moran <wmoran@collaborativefusion.com>
Cc: Matthew Wakeling <matthew@flymine.org>
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: Fri, 29 Aug 2008 00:45:20 -0400 (EDT)
Message-ID: <Pine.GSO.4.64.0808290039180.23621@westnet.com> (raw)
In-Reply-To: <20080828095325.3c95f867.wmoran@collaborativefusion.com>
References: <BAY124-W57D3654AF1159CAF8EAC19F5660@phx.gbl>
	<82bpze3ou8.fsf@mid.bfk.de>
	<alpine.DEB.1.10.0808271436210.907@asgard.lang.hm>
	<alpine.DEB.1.10.0808281411220.4454@aragorn.flymine.org>
	<20080828095325.3c95f867.wmoran@collaborativefusion.com>

On Thu, 28 Aug 2008, Bill Moran wrote:

> In linux, it's possible to tell the OOM killer never to consider
> certain processes for the axe, using /proc magic.  See this page:
> http://linux-mm.org/OOM_Killer
>
> Perhaps this should be in the PostgreSQL docs somewhere?

The fact that 
http://www.postgresql.org/docs/current/static/kernel-resources.html#AEN22218 
tells you to flat-out turn off overcommit is the right conservative thing 
to be in the documentation as I see it.  Sure, it's possible to keep it on 
but disable the worst side-effect in some kernels (looks like 2.6.11+, so 
no RHEL4 for example).  Trying to get into all in the manual is kind of 
pushing what's appropriate for the PostgreSQL docs I think.

--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD



view thread (65+ messages)  latest in thread

Message-ID: <Pine.GSO.4.64.0808290039180.23621@westnet.com>
Permalink:  ../Pine.GSO.4.64.0808290039180.23621@westnet.com/
Also on:    postgresql.org/message-id/Pine.GSO.4.64.0808290039180.23621@westnet.com

 · 

reply
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: gsmith@gregsmith.com, wmoran@collaborativefusion.com, matthew@flymine.org
  Subject: Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
  In-Reply-To: <Pine.GSO.4.64.0808290039180.23621@westnet.com>

* 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