Subject: Best practice running a shared DB hosting server
From: Thomas Jacob <jacob@internet24.de>
To: pgsql-admin@postgresql.org
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="=-b5wPPTqtSOBcg8qwUU7K"
Date: Wed, 13 Aug 2008 15:44:57 +0200
Message-Id: <1218635097.28547.28.camel@enterprise.ims-firmen.de>
Mime-Version: 1.0


--=-b5wPPTqtSOBcg8qwUU7K
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hello List,

I was wondering if there is something like
a best practice document for running
PostgreSQL (probably 8.3.3) securely in a shared
Web+DB hosting environment, where different
people without any administrative relationship
between them may run their databases on
the same server.

I am particularly interested in the
role, permission and schema layout.

Also I'm worried about the amount of information
available to ordinary DB users. For instance,
without revoking access to pg_catalog from
PUBLIC all users can see the usernames,
database names etc. of all other users. But
revoking the right from pg_catalog doesn't
seem to be an option, as this breaks
several features of the psql utility and probably
other things.

   Thanks & Best Regards,
           Thomas


--=-b5wPPTqtSOBcg8qwUU7K
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBIouVZgF9cFv867HwRAk0tAKC/hGK5Wu65dB1F3cPmUYpsTXVgwACePsly
ghA0N1LHutskEhn6LebkbRA=
=494H
-----END PGP SIGNATURE-----

--=-b5wPPTqtSOBcg8qwUU7K--