Re: db_user_namespace a "temporary measure" - Mailing list pgsql-hackers

From Tom Lane
Subject Re: db_user_namespace a "temporary measure"
Date
Msg-id 28978.1394593566@sss.pgh.pa.us
Whole thread Raw
In response to Re: db_user_namespace a "temporary measure"  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: db_user_namespace a "temporary measure"  (Andrew Dunstan <andrew@dunslane.net>)
Re: db_user_namespace a "temporary measure"  (Jaime Casanova <jaime@2ndquadrant.com>)
Re: db_user_namespace a "temporary measure"  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> On 03/11/2014 09:37 PM, Tom Lane wrote:
>> In particular, I'd like to see an exclusion that prevents local users
>> from having the same name as any global user, so that we don't have
>> ambiguity in GRANT and similar commands.  This doesn't seem simple to
>> enforce (if we supported partial indexes on system catalogs, it would
>> be ...) but surely this representation is more amenable to enforcing it
>> than the existing one.

> Should be workable if you're creating a local name - just check against 
> the list of global roles.

Concurrent creations won't be safe without some sort of locking scheme.
A unique index would be a lot better way of plugging that hole than a
system-wide lock on user creation.  But not sure how to define a unique
index that allows (joe, db1) to coexist with (joe, db2) but not with
(joe, 0).
        regards, tom lane



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: db_user_namespace a "temporary measure"
Next
From: Andrew Dunstan
Date:
Subject: Re: db_user_namespace a "temporary measure"