Re: Safe memory allocation functions

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: Safe memory allocation functions
Дата
Msg-id CA+TgmoYXN8jQcMgEYJTd1q4=NfPz_axo1Z7YUTTCaygdeF2QbA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Safe memory allocation functions  (Michael Paquier <michael.paquier@gmail.com>)
Ответы Re: Safe memory allocation functions  (Michael Paquier <michael.paquier@gmail.com>)
Список pgsql-hackers
On Fri, Jan 30, 2015 at 1:10 AM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> I wrote:
>> Yes, this refactoring was good for testing actually...
> Oops, I have been too hasty when sending previous patch, there was a
> bug related to huge allocations. Patch correcting this bug is
> attached.

Committed.  I didn't think we really need to expose two separate flags
for the aligned and unaligned cases, so I ripped that out.  I also
removed the duplicate documentation of the new constants in the
function header; having two copies of the documentation, one far
removed from the constants themselves, is a recipe for them eventually
getting out of sync.  I also moved the function to what I thought was
a more logical place in the file, and rearranged the order of tests
slightly so that, in the common path, we test only whether ret == NULL
and not anything else.

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



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Roger Pack
Дата:
Сообщение: Fwd: [GENERAL] 4B row limit for CLOB tables
Следующее
От: Heikki Linnakangas
Дата:
Сообщение: Re: Overhauling our interrupt handling (was Escaping from blocked send() reprised.)