Postgres Pro
Downloads
Home   >   mailing lists

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

From Craig James
Subject Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
Date
Msg-id 48CE6D0D.80509@emolecules.com
Whole thread Raw
In response to Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception  (Florian Weimer <fweimer@bfk.de>)
Responses Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception  (Florian Weimer <fweimer@bfk.de>)
List pgsql-performance
Tree view 
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
aterrabyte swap disk and disable overcommitted memory. 

Craig

pgsql-performance by date:

Previous
From: Florian Weimer
Date:
Subject: Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
Next
From: Florian Weimer
Date:
Subject: Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception