From: | Sean Davis <sdavis2(at)mail(dot)nih(dot)gov> |
---|---|
To: | <glenn(at)tangelosoftware(dot)com(dot)au>, "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: user manage their own pg_hba entries |
Date: | 2006-07-25 11:52:13 |
Message-ID: | C0EB7E2D.1D54%sdavis2@mail.nih.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
If this is the way you are going to set things up, then I would just set up
all the users to connect to all databases. Then, users can set permissions
for their databases to limit privileges. Doing what you suggest means
giving everyone in your group access to the postgres account, with ability
to edit the configuration file, pg_hba, and even to potentially delete
files. This is not a very safe (as in keeping things running smoothly) way
to work. Make one person in charge of adding new users to pg_hba would be
my two-cents worth of advice.
Sean
On 7/24/06 22:10, "Glenn Davy" <glenn(at)tangelosoftware(dot)net> wrote:
> Hi
> How do all you out there in postgres land who allow users who can create
> thier own databases, also allow them to then add their db to pg_hba.conf and
> then have
> postgres reload those permissions
>
> Glenn
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
From | Date | Subject | |
---|---|---|---|
Next Message | Glenn Davy | 2006-07-25 13:06:57 | Re: getting mdb(microsoft acess) file in postgresql |
Previous Message | A. Kretschmer | 2006-07-25 11:52:06 | Re: getting mdb(microsoft acess) file in postgresql |