From: | "C(dot) Bensend" <benny(at)bennyvision(dot)com> |
---|---|
To: | Chris Cameron <chris(at)upnix(dot)com> |
Cc: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Multiple Servers |
Date: | 2001-08-21 02:30:29 |
Message-ID: | Pine.BSO.4.33L2.0108202126420.18291-100000@fusion.bennyvision.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Mon, 20 Aug 2001, Chris Cameron wrote:
> Actually, that's my exact same problem AND setup.
>
> Making a user that can create databases, but not users is a decent idea.
> That's what I'll be doing for my more trusted users. However, beyond that
> it looks like the only choice is to run multipule postmasters.
Well, kinda... I don't want my users to be able to create
databases. I only want them to create tables, modify
tables, etc.
_I_, as the hosting provider, will create the database for
them. And I will add their user. From then on, said user
should only be able to create/modify/drop tables, etc, WITHIN
their own database.
Is running multiple postmasters the _only_ way to achieve this?
If so, this is not so good. :/
Benny
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You see, we're leveraging the synergies of our existing open source
solution, without reliance on a single vendor.
Or in english: We use samba cause NT sucks ass.
--greg(at)rage(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-08-21 02:33:31 | Re: Multiple Servers |
Previous Message | Chris Cameron | 2001-08-21 02:25:02 | Re: Multiple Servers |