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

From Bill Moran
Subject Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
Date
Msg-id 20080828095325.3c95f867.wmoran@collaborativefusion.com
Whole thread Raw
In response to Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception  (Matthew Wakeling <matthew@flymine.org>)
Responses Re: select on 22 GB table causes"An I/O error occured while sending to the backend." exception
Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
List pgsql-performance
In response to Matthew Wakeling <matthew@flymine.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@collaborativefusion.com
Phone: 412-422-3463x4023

pgsql-performance by date:

Previous
From: Matthew Wakeling
Date:
Subject: Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
Next
From: "Kevin Grittner"
Date:
Subject: Re: select on 22 GB table causes"An I/O error occured while sending to the backend." exception