From: Valentin Bogdanov <valiouk@yahoo.co.uk>
To: 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 16:22:18 +0000 (GMT)
Message-ID: <874031.98985.qm@web25806.mail.ukl.yahoo.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0808291653060.4454@aragorn.flymine.org>
In 2003 I met this guy who was doing Computation Fluid Dynamics and he had to use this software written by physics engineers in FORTRAN. 1 Gig of ram wasn't yet the standard for a desktop pc at that time but the software required at least 1 Gig just to get started. So I thought what is the problem after all you are supposed to be able to allocate upto 2G on a 32 bit system even if you don't quite have the memory and you have sufficiently big swat space. Still, the software didn't load on Windows. So, it seems that Windows does not overcommit.
regards
--- On Fri, 29/8/08, Matthew Wakeling <matthew@flymine.org> wrote:
> From: Matthew Wakeling <matthew@flymine.org>
> Subject: Re: [PERFORM] select on 22 GB table causes "An I/O error occured while sending to the backend." exception
> To: pgsql-performance@postgresql.org
> Date: Friday, 29 August, 2008, 4:56 PM
> 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?
>
> --
> Sent via pgsql-performance mailing list
> (pgsql-performance@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance
Send instant messages to your online friends http://uk.messenger.yahoo.com
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: valiouk@yahoo.co.uk
Subject: Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
In-Reply-To: <874031.98985.qm@web25806.mail.ukl.yahoo.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