Re: pgsql: Add new function dsa_allocate0.
Thomas Munro <thomas.munro@enterprisedb.com>
From: Thomas Munro <thomas.munro@enterprisedb.com>
To: Robert Haas <rhaas@postgresql.org>
Cc: pgsql-committers@postgresql.org
Date: 2017-02-17T03:03:32Z
Lists: pgsql-hackers
Attachments
- fix-dsa-allocate0.patch (application/octet-stream) patch
On Fri, Feb 17, 2017 at 11:34 AM, Thomas Munro <thomas.munro@enterprisedb.com> wrote: > On Fri, Feb 17, 2017 at 7:02 AM, Robert Haas <rhaas@postgresql.org> wrote: >> http://git.postgresql.org/pg/commitdiff/9acb85597f1223ac26a5b19a9345849c43d0ff54 > Hmm. This will segfault if you're out of memory. Or to provide a more useful response... maybe this should be like the attached? Or maybe people think that dsa_allocate should throw on failure to allocate, like palloc? -- Thomas Munro http://www.enterprisedb.com
Commits
-
Make dsa_allocate interface more like MemoryContextAlloc.
- 16be2fd10019 10.0 landed
-
Add new function dsa_allocate0.
- 9acb85597f12 10.0 cited