Re: One Role, Two Passwords

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>
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:12:30
Message-ID: AANLkTinMbm=A5vfXRU7n+DzuiUtwPdc7vqu302QAQSB1@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jan 20, 2011 at 9:07 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> * 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.

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.

To 9.2.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Farina 2011-01-21 02:14:22 Re: One Role, Two Passwords
Previous Message Robert Haas 2011-01-21 02:08:10 Re: REVIEW: EXPLAIN and nfiltered