On Jan21, 2011, at 03:14 , Daniel Farina wrote: > On Thu, Jan 20, 2011 at 6:12 PM, Robert Haas <robertmh...@gmail.com> wrote: >> On Thu, Jan 20, 2011 at 9:07 PM, Stephen Frost <sfr...@snowman.net> wrote: >>> * Robert Haas (robertmh...@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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
