From: | Tommi Maekitalo <t(dot)maekitalo(at)epgmbh(dot)de> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: psql \d option list overloaded |
Date: | 2004-01-09 10:19:45 |
Message-ID: | 200401091119.45778.t.maekitalo@epgmbh.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-general pgsql-hackers |
Hi,
>
> 2) (using information schema ... little better)
>
> SELECT table_name FROM information_schema.tables WHERE table_schema
> = 'public';
>
> or ...
>
...
I just looked at the information_schema. It is a very nice feature, but
difficult to use in psql.
I just wanted to see, what I can find here. After trying and rtfm I ended in
'\d information_schema.*'. I get a very large page wich is quite unreadable.
'\d' is normally very usable.
It would be better not to show the view-definition.
What if \d on views just show the column, type and attribute. \d+ would show
the full view-definition.
Tommi
--
Dr. Eckhardt + Partner GmbH
http://www.epgmbh.de
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2004-01-09 11:40:51 | Re: A cohesive sales message |
Previous Message | Thomas Swan | 2004-01-09 07:07:24 | Re: psql \d option list overloaded |
From | Date | Subject | |
---|---|---|---|
Next Message | CoL | 2004-01-09 12:19:02 | Re: Using indices with long unique IDs. |
Previous Message | D. Dante Lorenso | 2004-01-09 10:11:08 | Re: Using indices with long unique IDs. |
From | Date | Subject | |
---|---|---|---|
Next Message | ohp | 2004-01-09 12:54:22 | Strand COPY from problem |
Previous Message | Dennis Björklund | 2004-01-09 09:35:34 | Translations in distributions 2 |