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 08:36:40
Message-ID: 82d4j5ls9z.fsf@mid.bfk.de (view raw or flat)
Thread:
Lists: pgsql-performance
* 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).

-- 
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:11:25
Subject: Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
Previous:From: Merlin MoncureDate: 2008-09-15 02:49:14
Subject: Re: Choosing a filesystem

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