Re: version() output vs. 32/64 bits - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: version() output vs. 32/64 bits
Date
Msg-id 4963A532.6080306@hagander.net
Whole thread Raw
In response to Re: version() output vs. 32/64 bits  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Bruce Momjian wrote:
> Tom Lane wrote:
>> Bruce Momjian <bruce@momjian.us> writes:
>>> So what do we want to do for 8.4?  Add 32/64-bit version() indicator and
>>> add OUT parameters to the TODO list?
>> +1.  There seems a good case for making the 32/64bit distinction
>> visible somewhere, and the text version string is as good as anyplace.
> 
> OK, done with the attached patch, and autoconf run.  Magnus, would you
> add this change to the MSVC build?  Thanks.
> 
>   test=> select version();
>                                  version
>   --------------------------------------------------------------------------
> 
>    PostgreSQL 8.4devel on i386-pc-bsdi4.3.1, compiled by GCC 2.95.3, 32-bit
>   (1 row)
> 
> 

Done.

postgres=# select version();                           version
----------------------------------------------------------------PostgreSQL 8.4devel, compiled by Visual C++ build 1400,
32-bit
(1 row)

//Magnus


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: dblink vs SQL/MED - security and implementation details
Next
From: Tom Lane
Date:
Subject: Is it really such a great idea for spi.h to include the world?