Why repalloc() != realloc() ? - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Why repalloc() != realloc() ?
Date
Msg-id 20040602025718.GA518@dcc.uchile.cl
Whole thread Raw
Responses Re: Why repalloc() != realloc() ?  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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"



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Official Freeze Date for 7.5: July 1st, 2004
Next
From: Bruce Momjian
Date:
Subject: Re: Converting postgresql.conf parameters to kilobytes