Skip site navigation (1) Skip section navigation (2)

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: (view raw, whole thread or download thread mbox)
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


pgsql-hackers by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group