Re: psql \l error

SAKAIDA Masaaki <sakaida@psn.co.jp>

From: SAKAIDA Masaaki <sakaida@psn.co.jp>
To: Hiroshi Inoue <Inoue@tpf.co.jp>
Cc: Peter Eisentraut <peter_e@gmx.net>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@postgreSQL.org, Bruce Momjian <pgman@candle.pha.pa.us>
Date: 2000-05-04T01:54:21Z
Lists: pgsql-hackers
"Hiroshi Inoue" <Inoue@tpf.co.jp> wrote:

> > -----Original Message-----
> > From: SAKAIDA Masaaki [mailto:sakaida@psn.co.jp]
> > 
> > "Hiroshi Inoue" <Inoue@tpf.co.jp> wrote:
> > > 
> > > In general client libraries/applications have to keep backward 
> > > compatibility as possible,so it isn't enough for clients to be able to
> > > talk to the latest version of PostgreSQL servers.
> > > 
> > > Comments ?  
> > 
> >   I agree with you. 
> > 
> >   User doesn't know how the specification of the server has been 
> > changed. Therefore, it is natural that user believe that new 
> > psql can talk to older server. Because backward compatibility is 
> > a reasonable rule of the upgrading in generic client software.
> >
> 
> Hmm,sorry for my poor English.
> What I meant is a little different from yours.
> What I wanted was to know official opinions about backward
> compatibility of clients(not only psql)included in PostgreSQL's
> release.

  Sorry for my 10*poor English ;-)
  I understand what you meant.


> There's already your pgbash that keeps backward compatibility.

  In the next release pgbash-2.1(pgbash is a tool like bash+psql),

    pgbash(7.0-libpq) can talk to 6.5/7.0-server.
and pgbash(6.5-libpq) can talk to 6.5/7.0-server.

  pgbash will keep backward and forward compatibility as much as 
possible.

--
Regard,
SAKAIDA Masaaki -- Osaka, Japan