Skip site navigation (1) Skip section navigation (2)

Re: Schemas: status report, call for developers

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bill Cunningham <billc(at)ballydev(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org, pgsql-interfaces(at)postgresql(dot)org
Subject: Re: Schemas: status report, call for developers
Date: 2002-04-30 18:23:45
Message-ID: 21260.1020191025@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-interfaces
Bill Cunningham <billc(at)ballydev(dot)com> writes:
> I would think this should produce the following:

> test=# \d mytab
>         Table "bar.mytab"
>  Column |  Type   | Modifiers
> --------+---------+-----------
>  f1     | text    |
>  f1     | integer |

>         Table "foo.mytab"
>  Column |  Type   | Modifiers
> --------+---------+-----------
>  f2     | text    |
>  f3     | integer |

Even when schemas bar and foo are not in your search path?  (And,
perhaps, not even accessible to you?)

My gut feeling is that "\d mytab" should tell you about the same
table that "select * from mytab" would find.  Anything else is
probably noise to you --- if you wanted to know about foo.mytab,
you could say "\d foo.mytab".

However, \d is not a wildcardable operation AFAIR.  For the commands
that do take wildcard patterns (like \z), I'm not as sure what should
happen.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Andrew SullivanDate: 2002-04-30 18:38:28
Subject: Re: [HACKERS] Re : Solaris Performance - 64 bit puzzle
Previous:From: Bill CunninghamDate: 2002-04-30 17:45:45
Subject: Re: Schemas: status report, call for developers

pgsql-interfaces by date

Next:From: Oleg BartunovDate: 2002-04-30 18:41:47
Subject: Re: Schemas: status report, call for developers
Previous:From: Bill CunninghamDate: 2002-04-30 17:45:45
Subject: Re: Schemas: status report, call for developers

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group