Re: Per-Database Roles - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Per-Database Roles
Date
Msg-id CA+TgmoaRf=K1koGTgeDthFF0tO=PfEEM7b=cOzHxGi7oKeY61g@mail.gmail.com
Whole thread Raw
In response to Re: Per-Database Roles  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Per-Database Roles
List pgsql-hackers
On Thu, May 24, 2012 at 6:21 PM, Bruce Momjian <bruce@momjian.us> wrote:
> On Tue, May 22, 2012 at 10:19:12AM -0400, Robert Haas wrote:
>> In retrospect, I think the idea of shared catalogs was probably a bad
>> idea.  I think we should have made roles and tablespaces database
>> objects rather than shared objects, and come up with some ad-hoc
>> method of representing the set of available databases.  But that
>> decision seems to have been made sometime pre-1996, so the thought of
>> changing it now is pretty painful, but I can dream...
>
> Yes, pre-1996.  I think the fact that authentication/user names appear
> in pg_hba.conf really locked the user name idea into global objects, and
> we have never really been able to make a dent in that.

Eh?  Why would the presence of usernames in pg_hba.conf mean that they
have to be global objects?

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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Backends stalled in 'startup' state: index corruption
Next
From: Stephen Frost
Date:
Subject: Re: Per-Database Roles