Re: Best practice running a shared DB hosting server - Mailing list pgsql-admin

From Thomas Jacob
Subject Re: Best practice running a shared DB hosting server
Date
Msg-id 20080818182430.GB22324@internet24.de
Whole thread Raw
In response to Re: Best practice running a shared DB hosting server  ("Scott Marlowe" <scott.marlowe@gmail.com>)
Responses Re: Best practice running a shared DB hosting server  ("Scott Marlowe" <scott.marlowe@gmail.com>)
List pgsql-admin
On Mon, Aug 18, 2008 at 10:49:49AM -0600, Scott Marlowe wrote:
> On Mon, Aug 18, 2008 at 10:38 AM, Thomas Jacob <jacob@internet24.de> wrote:
> > I've changed my approach by revoking rights to schema public
> > from PUBLIC in the template1, and then granting all rights
> > to again just to the "main" user, and usage rights to
> > the additional users.
> >
> > So people aren't forced to use schemas.
>
> Not sure exactly what you mean.  Everything in pgsql lives in a
> schema, whether it's public or another schema.  By judicious use of
> the search_path settings you can make the use of such schemas nearly
> transparent to the users, but they're still there.

Sorry, that was very vague. Some people might just be used
to there being an explicit public schema. This is not very
likely, agreed, but if having access to the public schema is not
a security risk, then there is no need to force users to create additional
schemas if they don't want to.

pgsql-admin by date:

Previous
From: Thomas Jacob
Date:
Subject: Re: Best practice running a shared DB hosting server
Next
From: "Scott Marlowe"
Date:
Subject: Re: Best practice running a shared DB hosting server