Re: Default privileges for new databases (was Re: Can't import large objects in most recent cvs) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Default privileges for new databases (was Re: Can't import large objects in most recent cvs)
Date
Msg-id 7136.1033267043@sss.pgh.pa.us
Whole thread Raw
In response to Re: Default privileges for new databases (was Re: Can't import  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Default privileges for new databases (was Re: Can't import  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Can someone tell me where we are on this;  exactly what writability do
> we have in 7.3?

The current code implements what I suggested in that note, viz:
default permissions for new databases areowner = all rights (ie, create schema and create temp)public = create temp
rightonly
 
but template1 and template0 are set toowner (postgres user) = all rightspublic = no rights
by initdb.

Also, the "public" schema within template1 is empty but writable by
public.  This is annoying, but at least it's easy to fix if you
mess up --- you can DROP SCHEMA public CASCADE and then recreate
the schema.  (Or not, if you don't want to.)
        regards, tom lane


pgsql-hackers by date:

Previous
From: Lamar Owen
Date:
Subject: Re: 7.2.3?
Next
From: Tom Lane
Date:
Subject: Re: [PATCHES] Cascaded Column Drop