| From: | Rod Taylor <rbt(at)zort(dot)ca> |
|---|---|
| To: | Bruno Wolff III <bruno(at)wolff(dot)to> |
| Cc: | "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 15:30:06 |
| Message-ID: | 1027697407.307.16.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 2002-07-26 at 11:28, Bruno Wolff III wrote:
> On Fri, Jul 26, 2002 at 10:48:53 -0300,
> "Marc G. Fournier" <scrappy(at)hub(dot)org> wrote:
> >
> > Something to maybe add to the TODO list, if someone has the
> > time/inclination to work on it ...
> >
> > The problem with the current auth system, as I see it, is that you can't
> > easily have seperate user lists and passwords per database ... its shared
> > across the system ...
>
> If you look at the 7.3 docs you will see that you will be able to restrict
> access to databases by user or group name. If you use group name and have
> one group per database you will be able to administer access pretty easily.
> If you have a lot of databases you can use group names matching database
> names and not have to touch your conf file when making new databases.
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. Very minor issue, but it would be nice to
have the ability (for those selling PostgreSQL storage services).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-07-26 15:43:37 | Re: Oracle Decode Function |
| Previous Message | Bruno Wolff III | 2002-07-26 15:28:09 | Re: Password sub-process ... |