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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Florian Weimer <fweimer@xxxxxx>, PostgreSQL Performance <pgsql-performance@xxxxxxxxxxxxxx>, Matthew Wakeling <matthew@xxxxxxxxxxx>
Subject: Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
From: Craig James <craig_james@xxxxxxxxxxxxxx>
Date: Mon, 15 Sep 2008 07:11:25 -0700
In-reply-to: <82d4j5ls9z.fsf@xxxxxxxxxx>
References: <BAY124-W57D3654AF1159CAF8EAC19F5660@xxxxxxx> <82bpze3ou8.fsf@xxxxxxxxxx> <alpine.DEB.1.10.0808271436210.907@xxxxxxxxxxxxxx> <alpine.DEB.1.10.0808281411220.4454@xxxxxxxxxxxxxxxxxxx> <EADBB336-A14E-492C-A8CA-105C8F77A43A@xxxxxxxxxxx> <alpine.DEB.1.10.0808281702450.4454@xxxxxxxxxxxxxxxxxxx> <48B6EA7E.2090707@xxxxxxxxxxxxxx> <82d4j5ls9z.fsf@xxxxxxxxxx>
User-agent: Thunderbird 2.0.0.16 (Macintosh/20080707)

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

Follow-Ups:
- Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
  - From: Florian Weimer

References:
- select on 22 GB table causes "An I/O error occured while sending to the backend." exception
  - From: henk de wit
- Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
  - From: Florian Weimer
- Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
  - From: david
- Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
  - From: Matthew Wakeling
- Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
  - From: Steve Atkins
- Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
  - From: Matthew Wakeling
- Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
  - From: Craig James
- Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
  - From: Florian Weimer

Prev by Date: Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
Next by Date: Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
Previous by thread: Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
Next by thread: Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
Index(es):
- Date
- Thread

[Postgresql General] [Postgresql PHP] [PHP Users] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Yosemite]