pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Scott Marlowe <smarlowe@g2switchworks.com>
To: martial.bizel@free.fr
Cc: pgsql-performance@postgresql.org
Subject: Re: out of memory
Date: Tue, 14 Feb 2006 10:50:35 -0600
Message-ID: <1139935835.22740.188.camel@state.g2switchworks.com> (raw)
In-Reply-To: <1139934753.43f20621ba78d@imp1-g19.free.fr>
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>
	<1139933720.43f20218cfe3a@imp6-g19.free.fr>
	<1139934097.22740.182.camel@state.g2switchworks.com>
	<1139934753.43f20621ba78d@imp1-g19.free.fr>

On Tue, 2006-02-14 at 10:32, martial.bizel@free.fr wrote:
> command explain analyze crash with the "out of memory" error
> 
> I precise that I've tried a lot of values from parameters shared_buffer and
> sort_mem
> 
> now, in config file, values are :
> sort_mem=32768
> and shared_buffer=30000

OK, on the command line, try increasing the sort_mem until hash_agg can
work.  With a 4 gig machine, you should be able to go as high as needed
here, I'd think.  Try as high as 500000 or so or more.  Then when
explain analyze works, compare the actual versus estimated number of
rows.



view thread (23+ messages)  latest in thread

Message-ID: <1139935835.22740.188.camel@state.g2switchworks.com>
Permalink:  ../1139935835.22740.188.camel@state.g2switchworks.com/
Also on:    postgresql.org/message-id/1139935835.22740.188.camel@state.g2switchworks.com

 · 

reply
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: smarlowe@g2switchworks.com, martial.bizel@free.fr
  Subject: Re: out of memory
  In-Reply-To: <1139935835.22740.188.camel@state.g2switchworks.com>

* 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