Re: [COMMITTERS] pgsql: Add new function dsa_allocate0.
От | Michael Paquier |
---|---|
Тема | Re: [COMMITTERS] pgsql: Add new function dsa_allocate0. |
Дата | |
Msg-id | CAB7nPqTYsbw07vOEPpocUtNoeq6eACdonhGtHv-cuUiz65X16w@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [COMMITTERS] pgsql: Add new function dsa_allocate0. (Thomas Munro <thomas.munro@enterprisedb.com>) |
Список | pgsql-committers |
On Fri, Feb 17, 2017 at 12:03 PM, Thomas Munro <thomas.munro@enterprisedb.com> wrote: > 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? dp = dsa_allocate(area, size); - object = dsa_get_address(area, dp); - memset(object, 0, size); + if (DsaPointerIsValid(dp)) + memset(dsa_get_address(area, dp), 0, size); What you are proposing here looks like the right answer to me. Like dsa_allocate, dsa_allocate0 should allow users to fallback to other methods if what is returned is InvalidDsaPointer for consistency. -- Michael
В списке pgsql-committers по дате отправления: