Re: Safe memory allocation functions

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Safe memory allocation functions
Date: 2015-01-16 14:06:12
Message-ID: CAB7nPqTAOLjrihMfDzZ9hNYHCPMz-d8r77WJEmby-H_yoBzmvg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jan 16, 2015 at 8:47 AM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> Voting for palloc_noerror() as well.
And here is an updated patch using this naming, added to the next CF as well.
--
Michael

Attachment Content-Type Size
20150116_palloc_noerror.patch text/x-diff 27.7 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2015-01-16 14:08:51 Re: Safe memory allocation functions
Previous Message Merlin Moncure 2015-01-16 14:05:07 Re: hung backends stuck in spinlock heavy endless loop