From: | Peter Eisentraut <e99re41(at)DoCS(dot)UU(dot)SE> |
---|---|
To: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org, SAKAIDA <sakaida(at)psn(dot)co(dot)jp> |
Subject: | RE: psql \l error |
Date: | 2000-05-02 08:34:17 |
Message-ID: | Pine.GSO.4.02A.10005021027011.13753-100000@Iller.DoCS.UU.SE |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 2 May 2000, Hiroshi Inoue wrote:
> What kind of backward compatibity is required for psql etc..?
I thought psql was some sort of a reference application, so sticking to
prehistoric technology is not necessarily required. For example, outer
joins will simplify psql a great deal but that would really mean it stops
working for everybody else. Not sure.
The knowledge about the system catalogs is already pretty deep so keeping
track of changes across versions is similar to the initdb problem: either
we prohibit version differences outright (I thought that would be too
strict), we let it go until it fails (something that has been eliminated
for initdb), or we provide compabitibility. If someone wants to do the
latter, be my guest.
> Are there any documentations about it ?
Yes.
> Of cource it's preferable that client application/libraries aren't
> tied to a specific version of server application.
I agree. If someone has ideas that are not too ugly to live I'm sure we
could agree on them.
--
Peter Eisentraut Sernanders väg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2000-05-02 08:46:53 | Re: shmem_seq may be a bad idea |
Previous Message | Peter Eisentraut | 2000-05-02 08:26:49 | Re: psql \l error |