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

From Matthew Wakeling
Subject Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
Date
Msg-id alpine.DEB.1.10.0808291653060.4454@aragorn.flymine.org
Whole thread Raw
In response to Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception  (Craig James <craig_james@emolecules.com>)
Responses Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
List pgsql-performance
On Fri, 29 Aug 2008, Craig James wrote:
> Disable overcommitted memory.  There is NO REASON to use it on any modern
> server-class computer, and MANY REASONS WHY IT IS A BAD IDEA.

As far as I can see, the main reason nowadays for overcommit is when a
large process forks and then execs. Are there any other modern programs
that allocate lots of RAM and never use it?

Matthew

--
Nog:     Look! They've made me into an ensign!
O'Brien: I didn't know things were going so badly.
Nog:     Frightening, isn't it?

pgsql-performance by date:

Previous
From: Craig James
Date:
Subject: Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
Next
From: Greg Smith
Date:
Subject: Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception