From: Tom Lane <tgl@sss.pgh.pa.us>
To: Trent Pingenot <pintj@hotmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Permissions Scenerio
Date: Mon, 15 Sep 2008 18:02:04 -0400
Message-ID: <20309.1221516124@sss.pgh.pa.us> (raw)
In-Reply-To: <BAY105-W1914C2300B5F700EB8BC82A6520@phx.gbl>
References: <BAY105-W1914C2300B5F700EB8BC82A6520@phx.gbl>
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
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: tgl@sss.pgh.pa.us, pintj@hotmail.com
Subject: Re: Permissions Scenerio
In-Reply-To: <20309.1221516124@sss.pgh.pa.us>
* 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