Skip site navigation (1) Skip section navigation (2)

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

From: Florian Weimer <fweimer(at)bfk(dot)de>
To: Craig James <craig_james(at)emolecules(dot)com>
Cc: PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org>, Matthew Wakeling <matthew(at)flymine(dot)org>
Subject: Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
Date: 2008-09-15 14:15:38
Message-ID: 82ej3ljy0l.fsf@mid.bfk.de (view raw or flat)
Thread:
Lists: pgsql-performance
* Craig James:

>> There are some run-time environments which allocate huge chunks of
>> memory on startup, without marking them as not yet in use.  SBCL is in
>> this category, and also the Hotspot VM (at least some extent).
>
> I stand by my assertion: It never makes sense.  Do these
> applications allocate a terrabyte of memory?  I doubt it.

SBCL sizes its allocated memory region based on the total amount of
RAM and swap space.  In this case, buying larger disks does not
help. 8-P

-- 
Florian Weimer                <fweimer(at)bfk(dot)de>
BFK edv-consulting GmbH       http://www.bfk.de/
Kriegsstra├če 100              tel: +49-721-96201-1
D-76133 Karlsruhe             fax: +49-721-96201-99

In response to

Responses

pgsql-performance by date

Next:From: Craig JamesDate: 2008-09-15 14:25:58
Subject: Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
Previous:From: Craig JamesDate: 2008-09-15 14:11:25
Subject: Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group