| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Michael Fuhr <mike(at)fuhr(dot)org> |
| Subject: | Re: Information Schema DBMS VERSION wrong |
| Date: | 2005-08-03 08:31:46 |
| Message-ID: | 200508031031.47926.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Am Freitag, 29. Juli 2005 06:28 schrieb Tom Lane:
> > The following query doesn't return the version of PostgreSQL currently
> > running, but rather the version of initdb that initialized the cluster:
> Not sure if it was really thought about, but seeing that (a) you can get
> the current version from "select version()" and (b) there isn't any
> other way to get the initdb version, it seems like this behavior is
> fine.
I thought about this and I don't like it. It could just as well confuse
people who are in the name of portability or whatever are trying to move
their application to use the information schema. If we wanted to have a way
to get certain information, we should design an interface for it and not rely
on an accident.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2005-08-03 09:10:19 | Re: [PATCHES] Patch to fix plpython on OS X |
| Previous Message | Christopher Kings-Lynne | 2005-08-03 02:45:22 | Re: [8.0.3] Not dumping all sequences ... |