X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 723849DC823 for ; Tue, 14 Feb 2006 12:06:46 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 56987-02 for ; Tue, 14 Feb 2006 12:06:44 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from exchange.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by postgresql.org (Postfix) with ESMTP id 8A56C9DC81F for ; Tue, 14 Feb 2006 12:06:43 -0400 (AST) Received: from 10.10.1.37 ([10.10.1.37]) by exchange.g2switchworks.com ([10.10.1.2]) with Microsoft Exchange Server HTTP-DAV ; Tue, 14 Feb 2006 16:06:41 +0000 Received: from state.g2switchworks.com by mail.g2switchworks.com; 14 Feb 2006 10:06:41 -0600 Subject: Re: out of memory From: Scott Marlowe To: martial.bizel@free.fr Cc: Tom Lane , pgsql-performance@postgresql.org In-Reply-To: <1139933018.43f1ff5a5e542@imp6-g19.free.fr> References: <1139930651.43f1f61b04773@imp2-g19.free.fr> <15115.1139931169@sss.pgh.pa.us> <1139933018.43f1ff5a5e542@imp6-g19.free.fr> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1139933201.22740.179.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Tue, 14 Feb 2006 10:06:41 -0600 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.167 required=5 tests=[AWL=0.166, UNPARSEABLE_RELAY=0.001] X-Spam-Score: 0.167 X-Spam-Level: X-Archive-Number: 200602/159 X-Sequence-Number: 17145 On Tue, 2006-02-14 at 10:03, martial.bizel@free.fr wrote: > Thanks for your response, SNIP > if HashAgg operation ran out of memory, what can i do ? 1: Don't top post. 2: Have you run analyze? Normally when hash agg runs out of memory, the planner THOUGHT the hash agg would fit in memory, but it was larger than expected. This is commonly a problem when you haven't run analyze.