Re: inconsistent owners in newly created databases? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: inconsistent owners in newly created databases?
Date
Msg-id 7870.1083678462@sss.pgh.pa.us
Whole thread Raw
In response to Re: inconsistent owners in newly created databases?  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses Re: inconsistent owners in newly created databases?  (Fabien COELHO <coelho@cri.ensmp.fr>)
List pgsql-hackers
Fabien COELHO <coelho@cri.ensmp.fr> writes:
> I was thinking about something fuzzy enough as:

> UPDATE pg_catalog.pg_namespace
> SET nspowner=datdba, nspacl=NULL -- NULL means default rights...

> The later is simple and makes sense anyway for a newly created database.

No, I don't think it does.  The DBA presently can set up a site-wide
policy about use of "public" by altering its permissions in template1.
For example, he might revoke create access from most users.  People will
be surprised if that fails to carry over to created databases.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "scott.marlowe"
Date:
Subject: The features I'm waiting for.
Next
From: Fabien COELHO
Date:
Subject: Re: inconsistent owners in newly created databases?