From: | "Robert Haas" <robertmhaas(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Bruce Momjian" <bruce(at)momjian(dot)us>, "Brendan Jurd" <direvus(at)gmail(dot)com>, "Greg Sabino Mullane" <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: FWD: Re: Updated backslash consistency patch |
Date: | 2009-01-15 18:41:10 |
Message-ID: | 603c8f070901151041i5a7e64cejf7c9e1aff9813180@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> BTW, it might be worth pointing out that \d has never worked like that;
> for instance "\d pg_class" gives me an answer anyway. So holding up the
> table behavior as a model of consistency that other \d commands should
> emulate is a pretty weak argument to begin with.
So in 8.3.5, which is what I currently have in front of me:
\d lists all tables, sequences, views
\dt lists user tables only
\d *foo* shows detailed information on all user and system tables,
sequences, and views that have foo in the name
\dt *foo* lists (without detail) all user tables
\d foo shows detailed information about foo, regardless of whether foo
is a user or system object
\dt foo shows detailed information about foo, provided it is a user table
So it appears that \dt only switches to detail mode when given a
specific object, not when given a wildcard, whereas \d switches when
given either a wildcard or a specific object, and only lists when
given no arguments at all. I agree that is pretty weird.
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2009-01-15 18:42:01 | Re: Autovacuum daemon terminated by signal 11 |
Previous Message | Justin Pasher | 2009-01-15 18:35:24 | Re: Autovacuum daemon terminated by signal 11 |