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

From Robert Haas
Subject Re: Safe memory allocation functions
Date
Msg-id CA+Tgmob56c=ifUq6O0dBQymqUSuvjmOgPg6fPsaytFJU57uQCw@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
List pgsql-hackers
On Fri, Jan 16, 2015 at 10:56 AM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> So how about something like
>
> #define ALLOCFLAG_HUGE                  0x01
> #define ALLOCFLAG_NO_ERROR_ON_OOM       0x02
> void *
> MemoryContextAllocFlags(MemoryContext context, Size size, int flags);

That sounds good, although personally I'd rather have the name be
something like MemoryContextAllocExtended; we have precedent for using
"Extended" for this sort of thing elsewhere.  Also, I'd suggest trying
to keep the flag name short, e.g. ALLOC_HUGE and ALLOC_NO_OOM (or
ALLOC_SOFT_FAIL?).

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



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: moving from contrib to bin
Next
From: Michael Paquier
Date:
Subject: Re: Error check always bypassed in tablefunc.c