To: Trent Pingenot <pintj@hotmail.com>
cc: pgsql-admin@postgresql.org
Subject: Re: Permissions Scenerio 
In-reply-to: <BAY105-W1914C2300B5F700EB8BC82A6520@phx.gbl> 
References: <BAY105-W1914C2300B5F700EB8BC82A6520@phx.gbl>
Comments: In-reply-to Trent Pingenot <pintj@hotmail.com>
	message dated "Mon, 15 Sep 2008 15:07:22 -0600"
Date: Mon, 15 Sep 2008 18:02:04 -0400
Message-ID: <20309.1221516124@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Trent Pingenot <pintj@hotmail.com> writes:
> I've been a PostGres user for a while, but am just now having to implement some security for a project.  The hope is that we can create an environment through Roles that would allow users the ability to create a database(s) and have access to their database(s) but not have access to others' databases. I've been able to get part of the way there to create a user with createDB privileges and recording them in the pg_hba.conf file. However, when my test user creates a new database, they are the owner of that database but can't use it.  Is there a way to avoid having to add user /database entry in
> the pg_hba.conf file every time a user creates a new database?

Don't try to enforce per-database connect permissions in pg_hba.conf;
at least, not any such permissions you don't want to have to edit that
file to change.  Instead use GRANT/REVOKE CONNECT ON DATABASE.

			regards, tom lane