Re: Out of memory error in 8.1.0 Win32

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Out of memory error in 8.1.0 Win32
Date: 2006-06-19 03:13:11
Message-ID: 9259.1150686791@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Wes 2006-06-19 03:41:04 Adding foreign key constraints without integrity check?
Previous Message Tony Caduto 2006-06-19 02:50:58 Re: Question about openSSL