Re: Open 7.3 items - Mailing list pgsql-hackers

From Lamar Owen
Subject Re: Open 7.3 items
Date
Msg-id 200208141536.00145.lamar.owen@wgcr.org
Whole thread Raw
In response to Re: Open 7.3 items  (Vince Vielhaber <vev@michvhf.com>)
Responses Re: Open 7.3 items  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: Open 7.3 items  (Vince Vielhaber <vev@michvhf.com>)
List pgsql-hackers
On Wednesday 14 August 2002 03:29 pm, Vince Vielhaber wrote:
> Hate to complicate things more, but back to a global username, say
> you have user "lowen" that should have access to all databases.  What
> happens if there's already a lowen@somedb that's an unprivileged user.
> Assuming lowen is a db superuser, what happens in somedb?  If there's
> a global user "lowen" and you try to create a lowen@somedb later, will
> it be allowed?

If the user 'lowen' is then expanded to 'lowen@template1' it would be stored 
that way -- and lowen@template1 is different from lowen@pari, for instance.  
The lowen@template1 user could be a superuser and lowen@pari might not -- but 
they become distinct users.  Although I do understand the difficulty if the 
FQDU isn't stored in full in the appropriate places.  So I guess the solution 
is that wherever a user name is to be stored, the fully qualified form must 
be used and checked against, with @template1 being a 'this user is 
everywhere' shorthand.

But maybe I'm just misunderstanding the implementation.
-- 
Lamar Owen
WGCR Internet Radio
1 Peter 4:11


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: journaling in contrib ...
Next
From: "Marc G. Fournier"
Date:
Subject: Re: journaling in contrib ...