Re: The return value of allocate_recordbuf() - Mailing list pgsql-hackers

From Robert Haas
Subject Re: The return value of allocate_recordbuf()
Date
Msg-id CA+Tgmoay_=oK6+jtbqv21uOsKPGmWtyh2cfRVmd+eVF0cbgYgw@mail.gmail.com
Whole thread Raw
In response to Re: The return value of allocate_recordbuf()  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Responses Re: The return value of allocate_recordbuf()  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On Mon, Dec 29, 2014 at 6:14 AM, Heikki Linnakangas
<hlinnakangas@vmware.com> wrote:
> Hmm. There is no way to check beforehand if a palloc() will fail because of
> OOM. We could check for MaxAllocSize, though.

I think we need a version of palloc that returns NULL instead of
throwing an error.  The error-throwing behavior is for the best in
almost every case, but I think the no-error version would find enough
users to be worthwhile.

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: psql tab completion: fix COMMENT ON ... IS IS IS
Next
From: Thom Brown
Date:
Subject: Re: Parallel Seq Scan