From: | Jie Liang <jie(at)stbernard(dot)com> |
---|---|
To: | 'Tom Lane' <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | 'Bruce Momjian' <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: why schema name is same as username behaves different then ot |
Date: | 2002-12-05 23:45:51 |
Message-ID: | E7E213858379814A9AE48CA6754F5ECB1E192C@mail01.stbernard.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Got it.
Thank you.
Jie
-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Thursday, December 05, 2002 2:58 PM
To: Jie Liang
Cc: 'Bruce Momjian'; pgsql-admin(at)postgresql(dot)org
Subject: Re: why schema name is same as username behaves different then
others
Jie Liang <jie(at)stbernard(dot)com> writes:
> ####I expect to see something like:
You're neglecting the effects of search path. \dt only shows what's
visible in your search path. (IIRC, \dt *.* is the easiest way to
see all tables regardless of search path.)
> #### it seems if schema name is same as username then
> #### it will shadow the objects in the public schema that have same name.
That's what it's supposed to do, and yes this is documented, and yes
you can change it if you don't like it. Read about search_path.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jie Liang | 2002-12-05 23:50:29 | Re: why schema name is same as username behaves different then ot |
Previous Message | Joe Conway | 2002-12-05 23:44:15 | Re: why schema name is same as username behaves different |