| From: | Rod Taylor <rbt(at)zort(dot)ca> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruno Wolff III <bruno(at)wolff(dot)to>, "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Password sub-process ... |
| Date: | 2002-07-26 17:27:47 |
| Message-ID: | 1027704468.307.20.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 2002-07-26 at 11:48, Tom Lane wrote:
> Rod Taylor <rbt(at)zort(dot)ca> writes:
> > This still doesn't allow john on db1 to be a different user than john on
> > db2. To accomplish that (easily) we still need to install different
> > instances for each database.
>
> Some people think that cross-database user names are a feature, not
> a bug. I cannot see any way to change that without creating huge
> backward-compatibility headaches --- and it's not at all clear to
> me that it's a step forward, anyway.
I've been considering ways to come up with 2 classes of user. One which
is global, the other which is local. But it's not nearly enough of an
inconvenience to warrant it.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rod Taylor | 2002-07-26 17:49:30 | Re: Password sub-process ... |
| Previous Message | Bruno Wolff III | 2002-07-26 17:21:50 | Re: Password sub-process ... |