Re: Per-Database Roles

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Thom Brown <thom(at)linux(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Per-Database Roles
Date: 2012-05-26 02:23:09
Message-ID: CA+TgmoaRf=K1koGTgeDthFF0tO=PfEEM7b=cOzHxGi7oKeY61g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, May 24, 2012 at 6:21 PM, Bruce Momjian <bruce(at)momjian(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2012-05-26 02:34:54 Re: Per-Database Roles
Previous Message Tom Lane 2012-05-26 02:12:17 Re: Backends stalled in 'startup' state: index corruption