Hello 2008/12/31 Alvaro Herrera <alvhe...@commandprompt.com>: > Tom Lane wrote: >> Peter Eisentraut <pete...@gmx.net> writes: >> > On Wednesday 31 December 2008 04:45:01 Bruce Momjian wrote: >> >> PostgreSQL 8.4devel on i386-pc-bsdi4.3.1, compiled by GCC 2.95.3, 32-bit >> >> > Maybe we should separate all that, e.g., >> >> > SELECT version(); => 'PostgreSQL 8.4devel' >> > SELECT pg_host_os(); => 'bsdi4.3.1' >> > SELECT pg_host_cpu(); => 'i386' (although this is still faulty, as >> > per my >> > original argument; needs some thought) >> > SELECT pg_compiler(); => 'GCC 2.95.3' >> > SELECT pg_pointer_size(); => 4 (or 32) (this could also be a SHOW variable) >> >> Seems like serious overkill. No one has asked for access to individual >> components of the version string, other than the PG version number >> itself, which we already dealt with. > > 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. regards Pavel Stehule > -- > Alvaro Herrera http://www.CommandPrompt.com/ > The PostgreSQL Company - Command Prompt, Inc. > > -- > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers > -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers