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

From: Craig James <craig_james(at)emolecules(dot)com>
To: Florian Weimer <fweimer(at)bfk(dot)de>, 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:11:25
Message-ID: 48CE6D0D.80509@emolecules.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Florian Weimer wrote:
> * Craig James:
>> So it never makes sense to enable overcommitted memory when
>> Postgres, or any server, is running.
>
> 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. Buy a terrabyte swap disk and disable overcommitted memory.

Craig

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Florian Weimer 2008-09-15 14:15:38 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
Previous Message Florian Weimer 2008-09-15 08:36:40 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception