Re: Safe memory allocation functions

Michael Paquier <michael.paquier@gmail.com> writes:
> Attached is a patch adding the following set of functions for frontend
> and backends returning NULL instead of reporting ERROR when allocation
> fails:
> - palloc_safe
> - palloc0_safe
> - repalloc_safe

Unimpressed with this naming convention.  "_unsafe" would be nearer
the mark ;-)
        regards, tom lane