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
Views: Raw Message | Whole Thread | Download mbox | Resend email
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

Browse pgsql-performance by date

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