RE: psql \l error

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "SAKAIDA Masaaki" <sakaida(at)psn(dot)co(dot)jp>
Cc: "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgreSQL(dot)org>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>
Subject: RE: psql \l error
Date: 2000-05-04 01:05:08
Message-ID: 000b01bfb564$ca1516c0$2801007e@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: SAKAIDA Masaaki [mailto:sakaida(at)psn(dot)co(dot)jp]
>
> "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)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(at)tpf(dot)co(dot)jp

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message SAKAIDA Masaaki 2000-05-04 01:21:54 Re: psql \l error
Previous Message Tom Lane 2000-05-04 00:42:48 Re: shmem_seq may be a bad idea