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

Why repalloc() != realloc() ?

From: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
To: Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Why repalloc() != realloc() ?
Date: 2004-06-02 02:57:18
Message-ID: 20040602025718.GA518@dcc.uchile.cl (view raw or flat)
Thread:
Lists: pgsql-hackers
Hackers,

Is there a reason why repalloc() does not behave the same as realloc?
realloc(NULL, size) behaves the same as malloc(size), and it seems
useful behavior -- I wonder why repalloc() chooses to Assert() against
this exact condition?

I assume this is because the NULL pointer would not know what context it
belongs to, but the obvious answer is CurrentMemoryContext just like
palloc() does.  So there must be another reason.

Can this behavior be changed?

-- 
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"Para tener más hay que desear menos"


Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2004-06-02 03:00:03
Subject: Re: Converting postgresql.conf parameters to kilobytes
Previous:From: Andrew DunstanDate: 2004-06-02 02:15:32
Subject: Re: Official Freeze Date for 7.5: July 1st, 2004

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