RE: psql \l error
Hiroshi Inoue <inoue@tpf.co.jp>
From: "Hiroshi Inoue" <Inoue@tpf.co.jp>
To: "SAKAIDA Masaaki" <sakaida@psn.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:05:08Z
Lists: pgsql-hackers
> -----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. As for psql it isn't a generic client software as Peter mentioned. It's a part of backend in a sense. At least it could talk to pre-7.0 backend and it isn't so critical that \l,\df and \dd doesn't work for pre-7.0 backends. I'm not so much eager to change psql myself. There's already your pgbash that keeps backward compatibility. Regards. Hiroshi Inoue Inoue@tpf.co.jp