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?

			regards, tom lane

Responses

• Re: xmalloc => pg_malloc at 2012-10-02 16:19:13 from Andres Freund
• Re: xmalloc => pg_malloc at 2012-10-02 16:21:34 from Bruce Momjian
• Re: xmalloc => pg_malloc at 2012-10-04 04:27:33 from Peter Eisentraut

pgsql-hackers by date

Next:	From: Peter Geoghegan	Date: 2012-10-02 16:05:49
	Subject: Re: pgsql: Disable _FORTIFY_SOURCE with ICC
Previous:	From: Bruce Momjian	Date: 2012-10-02 15:58:57
	Subject: Re: [ADMIN] pg_upgrade from 9.1.3 to 9.2 failed