pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Alex Hochberger <alex@dsgi.us>
Cc: Richard Huxton <dev@archonet.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Configuring a Large RAM PostgreSQL Server
Date: Thu, 29 Nov 2007 16:29:19 -0300
Message-ID: <20071129192919.GJ9567@alvh.no-ip.org> (raw)
In-Reply-To: <8DC76DFA-C278-4C0C-A1FC-037257903BAD@dsgi.us>
References: <C78952BC-8F12-486E-9BD3-368EFAF448AD@dsgi.us>
	<474F0FC3.4000109@archonet.com>
	<8DC76DFA-C278-4C0C-A1FC-037257903BAD@dsgi.us>

> On Nov 29, 2007, at 2:15 PM, Richard Huxton wrote:

>> Alex Hochberger wrote:
>>>    Problem Usage: we have a 20GB table with 120m rows that we are 
>>> splitting into some sub-tables.  Generally, we do large data pulls from 
>>> here, 1 million - 4 million records at a time, stored in a new table for 
>>> export.  These queries are problematic because we are unable to index the 
>>> database for the queries that we run because we get out of memory errors.
>>
>> Would it not make sense to find out why you are getting these errors 
>> first?

Alex Hochberger wrote:
> It's not on rebuilding the index, it's on CREATE INDEX.
>
> I attribute it to wrong setting, Ubuntu bizarre-ness, and general problems.

Please do not top-post.  I reformatted your message for clarity.

Richard is still correct: it is not normal to get out-of-memory errors
during index building, regardless of age of servers and Linux distro.
Perhaps you just have a maintenance_work_mem setting that's too large
for your server.

-- 
Alvaro Herrera                        http://www.advogato.org/person/alvherre
"Uno puede defenderse de los ataques; contra los elogios se esta indefenso"



view thread (5+ messages)  latest in thread

Message-ID: <20071129192919.GJ9567@alvh.no-ip.org>
Permalink:  ../20071129192919.GJ9567@alvh.no-ip.org/
Also on:    postgresql.org/message-id/20071129192919.GJ9567@alvh.no-ip.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: alvherre@alvh.no-ip.org, alex@dsgi.us, dev@archonet.com
  Subject: Re: Configuring a Large RAM PostgreSQL Server
  In-Reply-To: <20071129192919.GJ9567@alvh.no-ip.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox