Re: xmalloc => pg_malloc - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: xmalloc => pg_malloc
Date
Msg-id 20121002162134.GF30089@momjian.us
Whole thread Raw
In response to xmalloc => pg_malloc  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Oct  2, 2012 at 12:02:13PM -0400, Tom Lane wrote:
> While looking around to fix the pg_malloc(0) issue, I noticed that
> various other pieces of code such as pg_basebackup have essentially
> identical functions, except they're called xmalloc().  I propose to
> standardize all these things on this set of names:
> 
>     pg_malloc
>     pg_malloc0    (for malloc-and-zero behavior)
>     pg_calloc    (randomly different API for pg_malloc0)
>     pg_realloc
>     pg_free
>     pg_strdup
> 
> Any objections?

Please standarize.  I am totally confused by the many memory
implementations we have.  (Pg_upgrade uses pg_malloc().)

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: xmalloc => pg_malloc
Next
From: Tom Lane
Date:
Subject: Re: xmalloc => pg_malloc