Added to TODO:
* Set proper permissions on non-system schemas during db creation
Currently all schemas are owned by the super-user because they are
copied from the template1 database.
---------------------------------------------------------------------------
Fabien COELHO wrote:
>
> Dear Bruce,
>
> > Is there a TODO here?
>
> I think yes. I would suggest an open entry like:
>
> . decide what a "database owner" is expected to be able do (esp. wrt acls)
> on non-system schema, e.g. "public", and then implement it.
> - should the database owner own the "public" schema by default?
> - what about other non-system schemas?
> - what about other objects?
>
> ISTM that it reflects that although the "what" is unclear, there is an
> issue somewhere;-)
>
> --
> Fabien Coelho - [EMAIL PROTECTED]
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to [EMAIL PROTECTED] so that your
> message can get through to the mailing list cleanly
>
--
Bruce Momjian | http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
