Re: Re: [COMMITTERS] pgsql: GIN index build's allocatedMemory counter needs to be long, not

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Re: [COMMITTERS] pgsql: GIN index build's allocatedMemory counter needs to be long, not
Дата
Msg-id 8337.1195419479@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Re: [COMMITTERS] pgsql: GIN index build's allocatedMemory counter needs to be long, not  (Peter Eisentraut <peter_e@gmx.net>)
Список pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> Jeremy Drake wrote:
>> I don't know if this has been discussed before, but you are aware that it
>> is not dictated by the C standard that sizeof(long) == sizeof(void*)?

> Yes, and there is lots of work left to do to support that.

Yeah.  The current code convention is to use "long" when counting space
allocations --- see tuplesort.c for instance --- so I made this do
likewise.  At some point we should try to migrate away from that,
but not today.
        regards, tom lane


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

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: Re: [COMMITTERS] pgsql: GIN index build's allocatedMemory counter needs to be long, not
Следующее
От: Dave Page
Дата:
Сообщение: Server maintenance