From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: db_user_namespace a "temporary measure" |
Date: | 2014-03-12 03:01:53 |
Message-ID: | 531FCE21.60901@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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. For creating global names, maybe we could keep
an invisible shared catalog (or maybe only visible to global superusers)
of local names / db oids. New global names would be checked against that
catalog. Something like that.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-03-12 03:06:06 | Re: db_user_namespace a "temporary measure" |
Previous Message | Tom Lane | 2014-03-12 01:37:47 | Re: db_user_namespace a "temporary measure" |