| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: List schema contents |
| Date: | 2006-06-09 20:55:07 |
| Message-ID: | 24709.1149886507@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-www |
"Jim C. Nasby" <jnasby(at)pervasive(dot)com> writes:
> What I'm looking for is what "\d" provides you, only limited to a
> specific schema. "\d information_schema." (for example) doesn't provide
> that; it provides the details for every table/view in
> information_schema.
What you're looking for is \dt, or perhaps \dtsv or one of those forms.
I'd be the first to agree that the behavior of \d isn't particularly
orthogonal, but it's not the pattern language that's the problem, it's
the command itself.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-06-09 21:00:01 | Re: List schema contents |
| Previous Message | Jim C. Nasby | 2006-06-09 20:42:47 | Parallel index build during COPY |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-06-09 21:00:01 | Re: List schema contents |
| Previous Message | Bruce Momjian | 2006-06-09 20:33:17 | Re: archive threads across months (was Re: [HACKERS] List |