Re: inconsistent owners in newly created databases?

From: Greg Stark <gsstark(at)mit(dot)edu>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: inconsistent owners in newly created databases?
Date: 2004-05-04 17:33:37
Message-ID: 873c6gyu4u.fsf@stark.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> writes:

> nspacl = aclitems_switch_grantor(nspacl, datdba)

Instead of having a hard coded list of template1 objects that need to be
chowned to the database owner. Perhaps there should be a special user like
dbowner which owns the schema and whatever other objects are necessary. Then
createdb would chown over anything owned by dbowner but not by objects owned
by postgres.

This would have the advantage that a dba could add objects to template1 and
choose whether to set them to be owned by postgres or owned by dbowner. Then
create various databases owned by different users and automatically have the
selected template objects be owned by the database owner.

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2004-05-04 18:18:48 Resource allocation?
Previous Message Bruce Momjian 2004-05-04 17:25:36 Function to do runtime relative directory mapping