From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Daniel Farina <drfarina(at)acm(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: One Role, Two Passwords |
Date: | 2011-01-21 02:07:14 |
Message-ID: | 20110121020714.GQ30352@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Robert Haas (robertmhaas(at)gmail(dot)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.
> It's always struck me that using multiple
> database logins would create all sorts of inconsistencies with
> different objects ending up owned by different users, but I guess
> until recently I was under the impression I was the only one who had
> an issue with that. It seems not.
Uh, no, you're definitely not alone. It's a huge pain in the ass,
imv.
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-01-21 02:08:10 | Re: REVIEW: EXPLAIN and nfiltered |
Previous Message | Robert Haas | 2011-01-21 02:06:34 | Re: REVIEW: EXPLAIN and nfiltered |