Re: Open 7.3 items

From: Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>
To: Vince Vielhaber <vev(at)michvhf(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Open 7.3 items
Date: 2002-08-14 20:34:13
Message-ID: 200208141634.13682.lamar.owen@wgcr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wednesday 14 August 2002 03:55 pm, Vince Vielhaber wrote:
> On Wed, 14 Aug 2002, Lamar Owen wrote:
> > If the user 'lowen' is then expanded to 'lowen(at)template1' it would be
> > stored that way -- and lowen(at)template1 is different from lowen(at)pari, for

> > But maybe I'm just misunderstanding the implementation.
>
> I may be too, but what's wrong with just "lowen" being shorthand for
> 'this user is everywhere'? Does it also mean that we'd have a user
> postgres(at)template1?

WE could still use the form without @template1, but the backend would assume
the @template1 user was being meant when the unqualified shorthand was used.
So the former plain 'postgres' user could still be such to us, to client
programs, etc, but the backend would assume that that meant
postgres(at)template1 -- no namespace collision, and the special case is that
anyone(at)template1 has the behavior the unadorned plain user now has.

I do see Bruce's points, however.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Lamar Owen 2002-08-14 21:01:06 Re: Open 7.3 items
Previous Message Neil Conway 2002-08-14 20:32:26 encrypted passwords