Skip site navigation (1) Skip section navigation (2)

Re: Memory management, palloc

From: Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>
To: Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Memory management, palloc
Date: 2001-03-08 14:54:29
Message-ID: 20010308155429.A11790@ara.zf.jcu.cz (view raw or flat)
Thread:
Lists: pgsql-hackers
On Thu, Mar 08, 2001 at 10:28:50PM +1100, Gavin Sherry wrote:
> Hi guys,
> 
> I've been looking through the memory management system today.
> 
> When a request is made for a memory memory chunk larger than
> ALLOC_CHUNK_LIMIT, AllocSetAlloc() uses malloc() to give the request its
> own block. The result is tested by AllocSetAlloc() to see if the memory
> was allocated.
> 
> Irrespective of this, a chunk can be returned which has not had memory
> allocated to it. There is no testing of the return status of
> palloc() through out the code. 

 I don't understand. If some memory is not obtain in AllocSetAlloc()
all finish with elog(ERROR). Not exists way how return insufficient 
space. Or not?

		Karel

-- 
 Karel Zak  <zakkr(at)zf(dot)jcu(dot)cz>
 http://home.zf.jcu.cz/~zakkr/
 
 C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2001-03-08 14:59:34
Subject: Depending on system install scripts (was Re: COBOL)
Previous:From: D'Arcy J.M. CainDate: 2001-03-08 12:50:15
Subject: PostgreSQL on multi-CPU systems

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group