Postgres Pro
Downloads
Home   >   mailing lists

Re: Safe memory allocation functions - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Safe memory allocation functions
Date
Msg-id CAB7nPqTEj5ftaxdt4PWFb3RDek4yTVNQdcZi__R2JzO1eSZGmg@mail.gmail.com
Whole thread Raw
In response to Re: Safe memory allocation functions  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Safe memory allocation functions
Re: Safe memory allocation functions
List pgsql-hackers
Tree view 
On Fri, Jan 16, 2015 at 12:57 AM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
>> I do think that "safe" is the wrong suffix.  Maybe palloc_soft_fail()
>> or palloc_null() or palloc_no_oom() or palloc_unsafe().
>
> I liked palloc_noerror() better myself FWIW.
Voting for palloc_noerror() as well.
-- 
Michael

pgsql-hackers by date:

Previous
From: Andreas Karlsson
Date:
Subject: Re: PATCH: Reducing lock strength of trigger and foreign key DDL
Next
From: Tom Lane
Date:
Subject: Re: segmentation fault in execTuples.c#ExecStoreVirtualTuple