From: martial.bizel@free.fr
To: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: out of memory
Date: Tue, 14 Feb 2006 17:15:20 +0100
Message-ID: <1139933720.43f20218cfe3a@imp6-g19.free.fr> (raw)
In-Reply-To: <1139933201.22740.179.camel@state.g2switchworks.com>
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>
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
>
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: martial.bizel@free.fr, smarlowe@g2switchworks.com, tgl@sss.pgh.pa.us
Subject: Re: out of memory
In-Reply-To: <1139933720.43f20218cfe3a@imp6-g19.free.fr>
* 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