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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>
Cc: "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org, "Bruce Momjian" <bruce(at)momjian(dot)us>
Subject: Re: version() output vs. 32/64 bits
Date: 2008-12-31 18:25:34
Message-ID: 13242.1230747934@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> writes:
> 2008/12/31 Alvaro Herrera <alvherre(at)commandprompt(dot)com>:
>> Maybe we could have a separate function which returned the info in
>> various columns (OUT params). Maybe it would be useful to normalize the
>> info as reported the buildfarm, which right now is a bit ad-hoc.

> All should be GUC read only variables - It is cheep.

Not as cheap as a single added function. If we need to provide these
fields broken out --- and no one has demonstrated any need to do so ---
then I'd support Alvaro's suggestion.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2008-12-31 18:27:10 SET TRANSACTION and SQL Standard
Previous Message Simon Riggs 2008-12-31 18:21:34 lazy_truncate_heap()