From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
---|---|
To: | hugues-vincent(dot)grislin(at)vif(dot)tm(dot)fr |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: out of memory |
Date: | 2005-04-26 18:05:49 |
Message-ID: | 1114538749.13303.1265.camel@state.g2switchworks.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, 2005-04-26 at 09:02, Hugues-Vincent Grislin wrote:
> Hello,
>
> I have a problem when i try to execute my request :
>
> ERROR: out of memory
> DETAIL: Failed on request of size 336.
>
> (I had execute the " VACCUM" before)
> It's a SELECT which contains several jointures (simple ones, 1-1).
> With 5 jointures there is no problem but with 6, i have this error.
>
> config :
> Postgres 7.4.7
> Linux Redhat 7.0
> RAM : 256 Mo
> swap : 256 Mo
>
> I found some threads about that but no answer.
> Thanks,
Have you analyzed the database? Try that first. If you still get an
out of memory error, try setting enable_hashagg off (set
enable_hashagg=false;) and then running the same query again and see if
it then works. If it does, post the result of
explain analyze YOURQUERYHERE
If it doesn't post the output of a plain explain, no analyze.
From | Date | Subject | |
---|---|---|---|
Next Message | mmiranda | 2005-04-26 18:12:49 | Re: UltraSPARC versus AMD |
Previous Message | Ying Lu | 2005-04-26 17:58:09 | About index - "a query or data manipulation command can use at most one index per table" |