| From: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net> |
| 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-27 19:35:41 |
| Message-ID: | 200208271535.41986.lamar.owen@wgcr.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tuesday 27 August 2002 03:19 pm, Bruce Momjian wrote:
> I think we need to resolve this discussion from a week ago. The current
> code is this:
I thought it WAS resolved, to do:
> global usernames are stored just like before, e.g. postgres
> local users are stored as user(at)dbname
> when connecting, global users add '@' to their names
> when connecting, local users use just their user name, no @dbname
> Tom likes this because it is the fewer global users who have to append
> the '@'.
At least that was my perception of the uneasy consensus reached.
Basically, this tags the @ as magic saying, during the client connect process,
'I'm GLOBAL, treat me differently'. Now that I actually understand how this
is supposed to work, which your four lines above elucidate nicely, I am in
more agreement than I was that this is the right answer to this issue.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-08-27 19:39:00 | Re: MemoryContextAlloc: invalid request size 1934906735 |
| Previous Message | Bruce Momjian | 2002-08-27 19:25:23 | Re: SET SCHEMA? |