Re: (resolution?) Re: [HACKERS] memory problem again - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: (resolution?) Re: [HACKERS] memory problem again
Date
Msg-id 199912072316.SAA13688@candle.pha.pa.us
Whole thread Raw
In response to Re: (resolution?) Re: [HACKERS] memory problem again  (Daniel Kalchev <daniel@digsys.bg>)
List pgsql-hackers
> (another not related bug, but still on memory allocation)
> Still - this does not explain why postgres cannot allocated more than 76 MB 
> (according to top) on BSD/OS (never did, actually - any previous version too), 
> while a simple malloc(1 MB) loop allocates up to the process limit.
> 
> Maybe at some time postrges tries to allocate 'larger' chunk, which the BSD/OS 
> malloc does not like?
> 

You can easily put in errlog(NOTICE...) and dump out the allocations to
see what is being requested.  It is also possible TOP display is not
accurate in some way.  Does ps vm flags show this too?

--  Bruce Momjian                        |  http://www.op.net/~candle maillist@candle.pha.pa.us            |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Parallel regress tests (was Re: FOREIGN KEY and
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Table aliases in delete statements?