Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 185576502BD for ; Fri, 29 Aug 2008 13:22:27 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 76673-09 for ; Fri, 29 Aug 2008 13:22:20 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from web25806.mail.ukl.yahoo.com (web25806.mail.ukl.yahoo.com [217.12.10.191]) by postgresql.org (Postfix) with SMTP id 9833D6501C1 for ; Fri, 29 Aug 2008 13:22:20 -0300 (ADT) Received: (qmail 99223 invoked by uid 60001); 29 Aug 2008 16:22:18 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.uk; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=yRAXS5ef03UFpd4Ou7vB1l/AK6bXFnm6SxDg4MQJw13mqJApliykNIptVcvlEiJmvHPetiFrqpyH2/ZaB9OtStyfU/2FPI1KIcKg99VNGwHT9Hqw8aG0pGSvD/zLvFM44T/lczjp1t0qBsxqOCgJXbcAz1dkgHhv0MR54/IsnGA=; X-YMail-OSG: oT9lSrEVM1m8fY7M9pbFzy7AbPSn8c5bncPJ5vOw8AJhJvucZDt_YuFFCuwSx4rZnxG_JGoFBhXTbeFWqcZi.C5ilVMqHBJ4FxZd5p3NwrtNQkBlAD2U7TxsJsKkhDPli.Mun1l2TjgOEIw9HrE2xNCT Received: from [62.254.183.162] by web25806.mail.ukl.yahoo.com via HTTP; Fri, 29 Aug 2008 16:22:18 GMT X-Mailer: YahooMailWebService/0.7.218.2 Date: Fri, 29 Aug 2008 16:22:18 +0000 (GMT) From: Valentin Bogdanov Reply-To: valiouk@yahoo.co.uk Subject: Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception To: pgsql-performance@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-ID: <874031.98985.qm@web25806.mail.ukl.yahoo.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200808/426 X-Sequence-Number: 31307 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 requ= ired at least 1 Gig just to get started. So I thought what is the problem a= fter 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 Windo= ws does not overcommit. regards --- On Fri, 29/8/08, Matthew Wakeling wrote: > From: Matthew Wakeling > 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=20 > > server-class computer, and MANY REASONS WHY IT IS A > BAD IDEA. >=20 > As far as I can see, the main reason nowadays for > overcommit is when a=20 > large process forks and then execs. Are there any other > modern programs=20 > that allocate lots of RAM and never use it? >=20 > Matthew >=20 > --=20 > 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? >=20 > --=20 > Sent via pgsql-performance mailing list > (pgsql-performance@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-performance=0A=0ASend instant me= ssages to your online friends http://uk.messenger.yahoo.com