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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: version() output vs. 32/64 bits
Date: 2009-01-05 18:07:55
Message-ID: 23777.1231178875@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)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.

I think the business about splitting up the string is mostly
lily-gilding, but if someone wants it enough to do it ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen R. van den Berg 2009-01-05 18:16:58 Re: QuickLZ compression algorithm (Re: Inclusion in the PostgreSQL backend for toasting rows)
Previous Message Robert Haas 2009-01-05 18:04:14 Re: QuickLZ compression algorithm (Re: Inclusion in the PostgreSQL backend for toasting rows)