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 152719DC81F for ; Tue, 14 Feb 2006 12:15:24 -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 59306-02 for ; Tue, 14 Feb 2006 12:15:22 -0400 (AST) X-Greylist: whitelisted by SQLgrey- Received: from smtp3-g19.free.fr (smtp3-g19.free.fr [212.27.42.29]) by postgresql.org (Postfix) with ESMTP id F27B89DC80A for ; Tue, 14 Feb 2006 12:15:21 -0400 (AST) Received: from imp6-g19.free.fr (imp6-g19.free.fr [212.27.42.6]) by smtp3-g19.free.fr (Postfix) with ESMTP id 6D95044422; Tue, 14 Feb 2006 17:15:21 +0100 (CET) Received: by imp6-g19.free.fr (Postfix, from userid 33) id EFBEA2E0F4; Tue, 14 Feb 2006 17:15:20 +0100 (MET) Received: from wormhole.x-echo.com (wormhole.x-echo.com [193.252.148.11]) by imp6-g19.free.fr (IMP) with HTTP for ; Tue, 14 Feb 2006 17:15:20 +0100 Message-ID: <1139933720.43f20218cfe3a@imp6-g19.free.fr> Date: Tue, 14 Feb 2006 17:15:20 +0100 From: martial.bizel@free.fr To: Scott Marlowe Cc: Tom Lane , pgsql-performance@postgresql.org Subject: Re: out of memory References: <1139930651.43f1f61b04773@imp2-g19.free.fr> <15115.1139931169@sss.pgh.pa.us> <1139933018.43f1ff5a5e542@imp6-g19.free.fr> <1139933201.22740.179.camel@state.g2switchworks.com> In-Reply-To: <1139933201.22740.179.camel@state.g2switchworks.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.5 X-Originating-IP: 193.252.148.11 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.646 required=5 tests=[AWL=0.096, NO_REAL_NAME=0.55] X-Spam-Score: 0.646 X-Spam-Level: X-Archive-Number: 200602/161 X-Sequence-Number: 17147 Yes, I've launched ANALYZE command before sending request. I precise that's postgres version is 7.3.4 > 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. > > ---------------------------(end of broadcast)--------------------------- > TIP 5: don't forget to increase your free space map settings >