Re: One Role, Two Passwords - Mailing list pgsql-hackers

From Florian Pflug
Subject Re: One Role, Two Passwords
Date
Msg-id 702246FD-DB04-475C-B4F6-D9B8AF8844C9@phlo.org
Whole thread Raw
In response to Re: One Role, Two Passwords  (Daniel Farina <drfarina@acm.org>)
List pgsql-hackers
On Jan21, 2011, at 03:14 , Daniel Farina wrote:
> On Thu, Jan 20, 2011 at 6:12 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>> On Thu, Jan 20, 2011 at 9:07 PM, Stephen Frost <sfrost@snowman.net> wrote:
>>> * Robert Haas (robertmhaas@gmail.com) wrote:
>>>> It strikes me that it would be useful to have a GUC that sets the
>>>> owner of any new objects you create (much as you can control their
>>>> default schemas using search_path).
>>> 
>>> There was a great deal of discussion along these lines over the summer
>>> of '09 (iirc) with regard to default owners and with the default
>>> privileges patch.  I encourage you to try and make it happen though.
>> 
>> I'm not likely to write a patch for it, but if someone else writes one
>> I would be willing to (a) support it and (b) subject to consensus,
>> commit it.
> 
> Wouldn't this require a client application to issue the GUC setting?
> Or could I somehow tell a role "You create objects as this user, and
> you cannot change this."

You could do ALTER ROLE SET default_owner TO <whatever>. Nothing would
prevent the user from resetting default_owner, though - but do you really
need to protect against that?

best regards,
Florian Pflug



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: ToDo List Item - System Table Index Clustering
Next
From: "Kevin Grittner"
Date:
Subject: Re: REVIEW: EXPLAIN and nfiltered