From: martial.bizel@free.fr
To: pgsql-performance@postgresql.org
Subject: Re: out of memory
Date: Wed, 15 Feb 2006 09:34:06 +0100
Message-ID: <1139992446.43f2e77e50629@imp6-g19.free.fr> (raw)
In-Reply-To: <1139935835.22740.188.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>
<1139933720.43f20218cfe3a@imp6-g19.free.fr>
<1139934097.22740.182.camel@state.g2switchworks.com>
<1139934753.43f20621ba78d@imp1-g19.free.fr>
<1139935835.22740.188.camel@state.g2switchworks.com>
Good morning,
I've increased sort_mem until 2Go !!
and the error "out of memory" appears again.
Here the request I try to pass with her explain plan,
Nested Loop (cost=2451676.23..2454714.73 rows=1001 width=34)
-> Subquery Scan "day" (cost=2451676.23..2451688.73 rows=1000 width=16)
-> Limit (cost=2451676.23..2451678.73 rows=1000 width=12)
-> Sort (cost=2451676.23..2451684.63 rows=3357 width=12)
Sort Key: sum(occurence)
-> HashAggregate (cost=2451471.24..2451479.63 rows=3357
width=12)
-> Index Scan using test_date on
queries_detail_statistics (cost=0.00..2449570.55 rows=380138 width=12)
Index Cond: ((date >= '2006-01-01'::date) AND
(date <= '2006-01-30'::date))
Filter: (((portal)::text = '1'::text) OR
((portal)::text = '2'::text))
-> Index Scan using query_string_pkey on query_string (cost=0.00..3.01
rows=1 width=34)
Index Cond: ("outer".query = query_string.id)
(11 rows)
Any new ideas ?,
thanks
MB.
> 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.
>
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
Subject: Re: out of memory
In-Reply-To: <1139992446.43f2e77e50629@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