Postgres Pro
Downloads
Home   >   mailing lists

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

From Robert Haas
Subject Re: Safe memory allocation functions
Date
Msg-id CA+TgmoaVHNf3k=6Drq8ZGcuVfgjvGNA3k6osM0G8Ep0CX8B7Sg@mail.gmail.com
Whole thread Raw
In response to Re: Safe memory allocation functions  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
Tree view 
On Thu, Jan 15, 2015 at 8:42 AM, Andres Freund <andres@2ndquadrant.com> wrote:
> On 2015-01-15 08:40:34 -0500, Robert Haas wrote:
>> I do think that "safe" is the wrong suffix.  Maybe palloc_soft_fail()
>> or palloc_null() or palloc_no_oom() or palloc_unsafe().
>
> palloc_or_null()?

That'd work for me, too.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Out-of-bounds write and incorrect detection of trigger file in pg_standby
Next
From: Robert Haas
Date:
Subject: Re: parallel mode and parallel contexts