To: Bill Cunningham <billc@ballydev.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>,
	pgsql-interfaces <pgsql-interfaces@postgresql.org>
Subject: Re: Schemas: status report, call for developers 
In-reply-to: <3CCF02AA.2000209@ballydev.com> 
References: <21020.1020187890@sss.pgh.pa.us> <3CCED849.5040400@ballydev.com>
	<21260.1020191025@sss.pgh.pa.us> <3CCF02AA.2000209@ballydev.com>
Comments: In-reply-to Bill Cunningham <billc@ballydev.com>
	message dated "Tue, 30 Apr 2002 13:46:34 -0700"
Date: Tue, 30 Apr 2002 17:16:33 -0400
Message-ID: <2032.1020201393@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Bill Cunningham <billc@ballydev.com> writes:
> So we now have a default schema name of the current user?
> ... This is exactly how DB2 operates, implict schemas for each user.

You can operate that way.  It's not the default though; the DBA will
have to explicitly do a CREATE SCHEMA for each user.  For instance:

test=# CREATE USER tgl;
CREATE USER
test=# CREATE SCHEMA tgl AUTHORIZATION tgl;
CREATE
test=# \c - tgl
You are now connected as new user tgl.
test=> select current_schemas();
 current_schemas
-----------------
 {tgl,public}			-- my search path is now tgl, public
(1 row)

-- this creates tgl.foo:
test=> create table foo(f1 int);
CREATE
test=> select * from foo;
 f1
----
(0 rows)

test=> select * from tgl.foo;
 f1
----
(0 rows)


If you don't create schemas then you get backwards-compatible behavior
(all the users end up sharing the "public" schema as their current
schema).

See the development-docs pages I mentioned before for details.

			regards, tom lane