| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, "D(dot) Dante Lorenso" <dante(at)lorenso(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: psql \d option list overloaded |
| Date: | 2004-01-04 18:53:36 |
| Message-ID: | 200401041953.36380.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-general pgsql-hackers |
Bruce Momjian wrote:
> I am starting to agree that our \d* handling is just too overloaded.
> Look at the option list from \?:
> Can anyone remember all those?
Yes.
> I like the idea of adding a new syntax to show that information using
> simple SQL command syntax, and putting it in the backend so all
> applications can access it. I know we have information schema, and
> maybe that can be used to make this simpler.
That's right.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex J. Avriette | 2004-01-04 19:13:22 | Re: psql \d option list overloaded |
| Previous Message | Mark Kirkwood | 2004-01-04 07:22:10 | Re: psql \d option list overloaded |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | A E | 2004-01-04 19:06:07 | Anything akin to an Evaluate Statement in Postgresql? |
| Previous Message | Mike Nolan | 2004-01-04 18:47:20 | Re: GetLastInsertID ? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex J. Avriette | 2004-01-04 19:13:22 | Re: psql \d option list overloaded |
| Previous Message | Peter Eisentraut | 2004-01-04 18:51:15 | Re: [HACKERS] Spinlock support for linux-hppa? |