From: Thomas Jacob <jacob@internet24.de>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Thomas Jacob <jacob@internet24.de>
Cc: Robert Treat <xzilla@users.sourceforge.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: Best practice running a shared DB hosting server
Date: Mon, 18 Aug 2008 20:24:30 +0200
Message-ID: <20080818182430.GB22324@internet24.de> (raw)
In-Reply-To: <dcc563d10808180949m98f1173nf5a0d2373bc4132e@mail.gmail.com>
References: <1218635097.28547.28.camel@enterprise.ims-firmen.de>
<dcc563d10808130757o45cdeb45jaa87cc09d0bdd837@mail.gmail.com>
<1218642490.28547.50.camel@enterprise.ims-firmen.de>
<200808181148.14557.xzilla@users.sourceforge.net>
<1219077495.18884.38.camel@enterprise.ims-firmen.de>
<dcc563d10808180949m98f1173nf5a0d2373bc4132e@mail.gmail.com>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: jacob@internet24.de, scott.marlowe@gmail.com, xzilla@users.sourceforge.net
Subject: Re: Best practice running a shared DB hosting server
In-Reply-To: <20080818182430.GB22324@internet24.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox