Re: version() output vs. 32/64 bits

Поиск
Список
Период
Сортировка
От Magnus Hagander
Тема Re: version() output vs. 32/64 bits
Дата
Msg-id 495B4D92.3000406@hagander.net
обсуждение исходный текст
Ответ на Re: version() output vs. 32/64 bits  (Bruce Momjian <bruce@momjian.us>)
Список pgsql-hackers
Bruce Momjian wrote:
> Tom Lane wrote:
>> Peter Eisentraut <peter_e@gmx.net> writes:
>>> ...  Moreover, there does not actually seem to be a 
>>> way to find out whether you have a 32-bit or a 64-bit build (except by 
>>> using OS tools).
>> I think the basic definition of "32 bit" or "64 bit", certainly for
>> our purposes, is sizeof(void *).  That is something that configure
>> could easily find out.  Or you could look at sizeof(size_t) which
>> it already does find out.
>>
>> I have no immediate proposal on how to factor that into the version
>> string.
> 
> I think the pointer size is part of the compiler, rather than the
> platform, so it should go after the compiler mention, e.g.:
> 
>   test=> select version();
>                                     version
>   --------------------------------------------------------------------------
>   
>    PostgreSQL 8.4devel on i386-pc-bsdi4.3.1, compiled by GCC 2.95.3, 32-bit
>   (1 row)
> 
> The attached patch modifies configure.in and updates a documentation mention.

You forgot a certain another build system ;-)

Should be trivial to add there though, if we choose to do it this way,
so that's not an objection in general.

//Magnus


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

Предыдущее
От: Simon Riggs
Дата:
Сообщение: Re: Hot standby and b-tree killed items
Следующее
От: Magnus Hagander
Дата:
Сообщение: Re: parallel restore