From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
Cc: | DANTE ALEXANDRA <ALEXANDRA(dot)DANTE(at)BULL(dot)NET>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: out of memory during query execution |
Date: | 2005-12-20 16:15:18 |
Message-ID: | 29983.1135095318@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> On Tue, Dec 20, 2005 at 01:35:03PM +0100, DANTE ALEXANDRA wrote:
>> You will find below the explain plan of one of the queries which has
>> finished with "out of memory". This query contains aggregate and a
>> sub-select with 6 joins :
> 1. Firstly, it could be the Hash node. Does the estimated number of
> matches in part (96000 rows) match reality?
Actually, the hash on "supplier" (3000000 rows) looks like a bigger
risk. But if this is 8.1 then there is code in there to spill oversize
hash tables to disk, so I don't understand where the memory is going.
The "out of memory" failure should have provoked a MemoryContextStats
report in the postmaster log. Are there a bunch of lines like
%s: %ld total in %ld blocks; %ld free (%ld chunks); %ld used
and if so could we see 'em?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-12-20 16:21:46 | Re: is this a bug or I am blind? |
Previous Message | Jaime Casanova | 2005-12-20 16:08:03 | Re: One DB not backed up by pg_dumpall |