Re: Do we want a xmalloc or similar function in the Backend?

Andres Freund <andres@2ndquadrant.com> writes:
> There are 70+ calls of malloc in the backend in the form of

> type* foo = malloc(sizeof(...));
> if(!foo)
>    elog(ERROR, "could not allocate memory");

> which is a bit annoying to write at times. Would somebody argue against 
> introducing a function that does the above named xmalloc() or malloc_or_die()?

99% of the time, you should be using palloc if that's the behavior you
want.  I think most of the malloc calls are in places where we want a
bit more control over the error response.
        regards, tom lane