work_mem = 262144
I'm still trying to figure out how to track the memory usage in
ExecutorState
-----Original Message-----
From: pgsql-general-owner@postgresql.org
[mailto:pgsql-general-owner@postgresql.org] On Behalf Of Tom Lane
Sent: Sunday, June 18, 2006 11:13 PM
To: Qingqing Zhou
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Out of memory error in 8.1.0 Win32
"Qingqing Zhou" <zhouqq@cs.toronto.edu> writes:
>> ExecutorState: 550339936 total in 123 blocks; 195005920 free (740144
>> chunks); 355334016 used
>> ...
>> HashBatchContext: 293593176 total in 44 blocks; 3107384 free (80
chunks);
>> 290485792 used
> Er, looks like a huge hash-join but not sure if it is a memory leak,
Tom?
A hash join could suck a lot of memory in HashBatchContext, but what
seems wrong about your report is all that memory in ExecutorState.
Please see if you can track where that went.
BTW, what was work_mem set to in this example? In theory the
HashBatchContext shouldn't get much bigger than work_mem.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
