Re: psql \d option list overloaded

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Greg Stark <gsstark(at)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: psql \d option list overloaded
Date: 2004-01-11 17:18:05
Message-ID: 16985.1073841485@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-general pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Tom Lane wrote:
>> 2. Some people aren't using psql.

> I don't see why this is an issue. People not using psql are either
> using a GUI, which presumably supports plenty of "show" and "describe"
> functionality, or they're writing their own program, in which case it
> doesn't really matter how short or easy to remember the commands are.

But this interacts with point 3 (psql breaks on every new backend
version). It's not desirable to have every GUI and large custom program
implementing its own set of metadata inquiry commands: they all have
to go through the same update pain as psql. Perhaps if people start to
rely on information_schema for those things, life will get better,
but I'm unconvinced that will happen. psql itself certainly hasn't
moved in that direction.

regards, tom lane

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Robert Bernier 2004-01-11 17:30:54 Re: (not) powered by PostgreSQL
Previous Message Marc G. Fournier 2004-01-11 17:09:19 Re: (not) powered by PostgreSQL

Browse pgsql-general by date

  From Date Subject
Next Message Sai Hertz And Control Systems 2004-01-11 17:32:54 Re: IEEE 754 Conclusion
Previous Message David Garamond 2004-01-11 16:51:17 Re: CHAR(N) storage requirement

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-01-11 17:28:53 Re: PQinSend question
Previous Message Tom Lane 2004-01-11 17:12:31 Re: libpq thread safety