Re: psql \l error - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: psql \l error
Date
Msg-id 200005021114.HAA08878@candle.pha.pa.us
Whole thread Raw
In response to Re: psql \l error  (Hiroshi Inoue <Inoue@tpf.co.jp>)
Responses RE: psql \l error  ("Hiroshi Inoue" <Inoue@tpf.co.jp>)
List pgsql-hackers
> Peter Eisentraut wrote:
> 
> > 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:
> 
> Yes there's another example. PostgreSQL odbc driver wasn't able to talk
> to 7.0 backend until recently due to the change int28 -> int2vector.
> Now odbc driver could talk to all the backends from 6.2.
> We may have to hold some reference table between system catalogs
> and client appl/lib.

The big reason for the change is that int2vector is now more than 8
int2's (now 16), so there may be internal changes as well as a name
change for applications.

--  Bruce Momjian                        |  http://www.op.net/~candle pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Thomas Lockhart
Date:
Subject: Re: Request for 7.0 JDBC status
Next
From: Peter Mount
Date:
Subject: RE: Request for 7.0 JDBC status