Received: from localhost (unknown [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id E106D2E3209 for ; Thu, 29 Nov 2007 15:29:36 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 08440-05-2 for ; Thu, 29 Nov 2007 15:29:28 -0400 (AST) Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by postgresql.org (Postfix) with ESMTP id 9FB192E1EFF for ; Thu, 29 Nov 2007 15:29:29 -0400 (AST) Received: from perhan.alvh.no-ip.org (200-126-98-252.bk7-dsl.surnet.cl [200.126.98.252]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id lATJTK6d008564 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 29 Nov 2007 11:29:22 -0800 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 5C77747C0F; Thu, 29 Nov 2007 16:29:19 -0300 (CLST) Date: Thu, 29 Nov 2007 16:29:19 -0300 From: Alvaro Herrera To: Alex Hochberger Cc: Richard Huxton , pgsql-performance@postgresql.org Subject: Re: Configuring a Large RAM PostgreSQL Server Message-ID: <20071129192919.GJ9567@alvh.no-ip.org> References: <474F0FC3.4000109@archonet.com> <8DC76DFA-C278-4C0C-A1FC-037257903BAD@dsgi.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8DC76DFA-C278-4C0C-A1FC-037257903BAD@dsgi.us> User-Agent: Mutt/1.5.16 (2007-06-11) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Thu, 29 Nov 2007 11:29:23 -0800 (PST) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/383 X-Sequence-Number: 27798 > 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"