Re: Multiple Servers

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Chris Cameron <chris(at)upnix(dot)com>
Cc: "C(dot) Bensend" <benny(at)bennyvision(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: Multiple Servers
Date: 2001-08-21 03:56:56
Message-ID: 200108210356.f7L3uuS09849@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

> Alright,
>
> Seems the general problem is that people (me and "Benny") want to do what
> can be done with MySQL and be able to add a user, give them their own DB to
> play with, and leave it at that. However, Postgres doesn't seem to have as
> slick of a way to do such a thing because to let a user have control over
> their own database, they would have had to of been able to create the DB.
> And if they were able to create the DB, they'd be able to make others.
>
> I managed to do this (albeit not very gracefully). I created the user
> 'test' and game him permission to create DB's. Made a database with his
> username, then took away his ability to create databases. This allowed him
> to fool with his own DB (because he created it), but he could no longer
> create new DB's.
>
> Still, this seems like a bit of a crummy way to accomplish such a thing. I
> haven't been around PostgreSQL long enough to know how development takes
> place, but this is a decent feature to have in a DB I figure.

This is a valid inconvenience. Seems we should allow a createdb option
to set the database owner.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Gary Stainburn 2001-08-21 09:03:50 Re: Multiple Servers
Previous Message Chris Cameron 2001-08-21 03:09:07 Re: Multiple Servers