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

From: Matthew Wakeling <matthew(at)flymine(dot)org>
To: 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-29 15:56:30
Message-ID: alpine.DEB.1.10.0808291653060.4454@aragorn.flymine.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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?

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Greg Smith 2008-08-29 16:15:17 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
Previous Message Craig James 2008-08-29 15:25:51 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception