From: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
---|---|
To: | Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Memory management, palloc |
Date: | 2001-03-08 15:19:14 |
Message-ID: | Pine.LNX.4.21.0103090218390.11367-100000@linuxworld.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Karel,
On Thu, 8 Mar 2001, Karel Zak wrote:
> 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?
Ahh. Of course. My mistake =)
Gavin
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-03-08 16:35:51 | Re: WAL does not recover gracefully from out-of-disk-space |
Previous Message | Tom Lane | 2001-03-08 15:14:12 | Re: Memory management, palloc |