Re: Out of memory error in 8.1.0 Win32

From: Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>
To: "Relyea, Mike" <Mike(dot)Relyea(at)xerox(dot)com>
Cc: pgsql-general(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Out of memory error in 8.1.0 Win32
Date: 2006-06-22 03:01:14
Message-ID: Pine.LNX.4.58.0606212258190.30714@eon.cs
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On Wed, 21 Jun 2006, Relyea, Mike wrote:

> ExecutorState: 550339936 total in 123 blocks; 195003544 free (740135
> chunks); 355336392 used
> HashBatchContext: 293593176 total in 44 blocks; 3107384 free (80
> chunks); 290485792 used
> TIDBitmap: 2088960 total in 8 blocks; 924720 free (27 chunks); 1164240
> used
> HashBatchContext: 41877664 total in 11 blocks; 4845648 free (15 chunks);
> 37032016 used
> TIDBitmap: 2088960 total in 8 blocks; 1012120 free (27 chunks); 1076840
> used

The same problem. ExecutorState uses much more memory than we expect --
but not sure where they are from :-(

Regards,
Qingqing

Responses

Browse pgsql-general by date

  From Date Subject
Next Message John Tregea 2006-06-22 03:39:12 Return the primary key of a newly inserted row?
Previous Message Gurjeet Singh 2006-06-22 01:19:57 Re: SQL query question

Browse pgsql-hackers by date

  From Date Subject
Next Message Qingqing Zhou 2006-06-22 03:31:56 Problem to "current-status information in shared memory" patch
Previous Message Bruce Momjian 2006-06-22 02:13:03 Re: Overhead for stats_command_string et al, take 2