Re: psql, 7.4, and the \d command

From: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Brendan Jurd <blakjak(at)blakjak(dot)sytes(dot)net>, PostgreSQL-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: psql, 7.4, and the \d command
Date: 2004-02-17 17:19:56
Message-ID: Pine.LNX.4.33.0402171019130.30606-100000@css120.ihs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, 17 Feb 2004, Tom Lane wrote:

> Brendan Jurd <blakjak(at)blakjak(dot)sytes(dot)net> writes:
> > I'm not objecting to the incompatibility itself, but I do think more
> > information needs to be provided to the user. I humbly suggest that if
> > psql is not going to be fully backwards-compatible with previous
> > postgres backends, at the very least you should issue a warning when
> > psql connects to a partially compatible server.
>
> This has been discussed before. I think the reason for not doing it
> has been the difficulty of coming up with a useful warning that explains
> what will work and what won't. You suggest
>
> > WARNING: psql version is 7.4.1, but postgres server version is 7.3.4.
> > Some psql features may not function as expected.
>
> but you've got to admit that's pretty vague and unhelpful.

I'd rather something like:

WARNING: psql/pgsql client server version mismatch.
Things will break. You're on your own.

:-) At least it's honest

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ben 2004-02-17 17:43:24 Re: making tsearch2 dictionaries
Previous Message Oleg Bartunov 2004-02-17 16:51:03 Re: making tsearch2 dictionaries