Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception

From: Bill Moran <wmoran(at)collaborativefusion(dot)com>
To: Matthew Wakeling <matthew(at)flymine(dot)org>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
Date: 2008-08-28 13:53:25
Message-ID: 20080828095325.3c95f867.wmoran@collaborativefusion.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

In response to Matthew Wakeling <matthew(at)flymine(dot)org>:
>
> Probably the best solution is to just tell the kernel somehow to never
> kill the postmaster.

This thread interested me enough to research this a bit.

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?

--
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/

wmoran(at)collaborativefusion(dot)com
Phone: 412-422-3463x4023

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Kevin Grittner 2008-08-28 14:48:21 Re: select on 22 GB table causes"An I/O error occured while sending to the backend." exception
Previous Message Matthew Wakeling 2008-08-28 13:26:59 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception