Re: [HACKERS] Schemas: status report, call for developers

Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > I am a little uncomfortable about this.  It means that CREATE TABLE will
> > create a table in 'public' if the user doesn't have a schema of their
> > own, and in their private schema if it exists.  I seems strange to have
> > such a distinction based on whether a private schema exists.  Is this OK?
> 
> You have a better idea?
> 
> Given that we want to support both backwards-compatible and SQL-spec-
> compatible behavior, I think some such ugliness is inevitable.

I don't have a better idea, but I am wondering how this will work.  If I
create a schema with my name, does it get added to the front of my
schema schema search path automatically, or do I set it with SET,
perhaps in my per-user startup SET column?

If I want to prevent some users from creating tables in my database, do
I remove CREATE on the schema using REVOKE SCHEMA, then create a schema
for every user using the database?

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026