| From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
|---|---|
| To: | Robert Haas <rhaas(at)postgresql(dot)org> |
| Cc: | pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql: Add new function dsa_allocate0. |
| Date: | 2017-02-17 03:03:32 |
| Message-ID: | CAEepm=0soDK45-O6itxMH2QE+bVp6QvMuxVSnRu51AUxdDivDA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Fri, Feb 17, 2017 at 11:34 AM, Thomas Munro
<thomas(dot)munro(at)enterprisedb(dot)com> wrote:
> On Fri, Feb 17, 2017 at 7:02 AM, Robert Haas <rhaas(at)postgresql(dot)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
| Attachment | Content-Type | Size |
|---|---|---|
| fix-dsa-allocate0.patch | application/octet-stream | 483 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-02-17 03:09:20 | Re: pgsql: Add new function dsa_allocate0. |
| Previous Message | Thomas Munro | 2017-02-16 22:34:45 | Re: pgsql: Add new function dsa_allocate0. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-02-17 03:09:20 | Re: pgsql: Add new function dsa_allocate0. |
| Previous Message | Stephen Frost | 2017-02-17 02:34:48 | Re: SUBSCRIPTIONS and pg_upgrade |