Received: from localhost (unknown [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id C84472E0115 for ; Thu, 29 Nov 2007 15:15:25 -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 01394-10 for ; Thu, 29 Nov 2007 15:15:18 -0400 (AST) Received: from ptb-relay02.plus.net (ptb-relay02.plus.net [212.159.14.213]) by postgresql.org (Postfix) with ESMTP id A2C282E00E1 for ; Thu, 29 Nov 2007 15:15:19 -0400 (AST) Received: from [84.51.143.99] (helo=server3.office.archonet.com) by ptb-relay02.plus.net with esmtp (Exim) id 1Ixoqy-0002mZ-IS; Thu, 29 Nov 2007 19:15:16 +0000 Received: from [192.168.1.36] (dell36.office.archonet.com [192.168.1.36]) by server3.office.archonet.com (Postfix) with ESMTP id 1A05F27406A; Thu, 29 Nov 2007 19:15:16 +0000 (GMT) Message-ID: <474F0FC3.4000109@archonet.com> Date: Thu, 29 Nov 2007 19:15:15 +0000 From: Richard Huxton User-Agent: Thunderbird 2.0.0.9 (X11/20071031) MIME-Version: 1.0 To: Alex Hochberger CC: pgsql-performance@postgresql.org Subject: Re: Configuring a Large RAM PostgreSQL Server References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/381 X-Sequence-Number: 27796 Alex Hochberger wrote: > Does anyone have any white papers or basic guides for a large RAM server? > > We are consolidating two databases to enable better data-mining that > currently run on a 4 GB and 2 GB machine. The data issues on the 4 GB > machine are numerous, things like "create index" fail and update queries > fail from out of memory issues. > 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? It's not normal to get "out of memory" when rebuilding an index. -- Richard Huxton Archonet Ltd