Re: psql \d option list overloaded

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: psql \d option list overloaded
Date: 2004-01-10 19:15:19
Message-ID: 11694.1073762119@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-general pgsql-hackers

Greg Stark <gsstark(at)mit(dot)edu> writes:
> So for example:

> \describe table foo => \dt foo
> \describe index foo => \di foo
> \describe aggregate foo => \da foo
> \describe operator foo => \do foo

It doesn't seem to me that this buys much except verboseness, though.

ISTM there are three fundamental problems with \d and friends:

1. Some people have a hard time remembering the commands.
2. Some people aren't using psql.
3. psql keeps breaking across backend versions because the
needed commands change.

I don't see a lot of value in addressing just one of these problem
areas, when we could instead do something that addresses all three.

regards, tom lane

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Jon Jensen 2004-01-11 00:16:58 Re: psql \d option list overloaded
Previous Message Greg Stark 2004-01-10 18:28:08 Re: psql \d option list overloaded

Browse pgsql-general by date

  From Date Subject
Next Message Eric Freeman 2004-01-10 20:36:30 Any way to SELECT a list of table names?
Previous Message Tom Lane 2004-01-10 19:10:31 Re: postgresql dies without saying why

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2004-01-10 23:03:04 Re: Encoding problems in PostgreSQL with XML data
Previous Message Shachar Shemesh 2004-01-10 18:55:42 Re: OLE DB driver