| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | Chris Cameron <ccameron(at)powersurfr(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Managing Users |
| Date: | 2001-10-16 15:57:59 |
| Message-ID: | Pine.BSF.4.21.0110160856290.16557-100000@megazone23.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, 15 Oct 2001, Chris Cameron wrote:
> I'm having a bit of a problem managing users.
>
> I have a database owned by user joe. Joe has a bunch of tables in this
> database and is allowed to create databases but not users. All the
> tables are owned by joe.
> If I create another user without any privledges at all, that user is
> able to (on my system) create tables in any existing databases.
> Including joes database.
>
> Do I have something improperly configured, or is this just the way
> Postgres works? I realize I have little details, but I'm not entirely
> sure whats causing this so I don't know what details to include.
Right now, if a user can connect to a database, they can create objects.
You can make it impossible for the user to connect to the database by
using the pg_hba.conf to disallow the connections, but that's as far
as it goes.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jochem van Dieten | 2001-10-16 16:06:36 | Re: Sorting by parent/child relationships |
| Previous Message | Stephan Szabo | 2001-10-16 15:55:32 | Re: "Relation x does not exist" error when x does exist |