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

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: Re: [COMMITTERS] pgsql: GIN index build's allocatedMemory counter needs to be long, not
Дата
Msg-id 200711182146.43503.peter_e@gmx.net
обсуждение исходный текст
Ответ на Re: [COMMITTERS] pgsql: GIN index build's allocatedMemory counter needs to be long, not  (Jeremy Drake <pgsql@jdrake.com>)
Ответы Re: Re: [COMMITTERS] pgsql: GIN index build's allocatedMemory counter needs to be long, not  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
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*)?

As evidenced by this piece of code in postgres.h:

typedef unsigned long Datum;    /* XXX sizeof(long) >= sizeof(void *) */

> The best counter-example I know is Windows x64, where sizeof(long) == 4
> while sizeof(void*) == 8.

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

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/


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

Предыдущее
От: Jeremy Drake
Дата:
Сообщение: 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