From: Isaac Dover <isaacdover@gmail.com>
To: pgsql-sql@postgresql.org
Subject: Re: help with pg_hba.conf
Date: Fri, 22 May 2009 13:39:43 -0400
Message-ID: <b560e3300905221039r4c8cc072o3dfb54c5a6a9509f@mail.gmail.com> (raw)
In-Reply-To: <26711.1243009898@sss.pgh.pa.us>
References: <b560e3300905212337r6c7c1932i3192818835f99f69@mail.gmail.com>
<b560e3300905220603w8444c87ib0eb4c89dfc13114@mail.gmail.com>
<26711.1243009898@sss.pgh.pa.us>
thank you _SO_ much. I'm not sure how I overlooked that, but it is far
easier to manage using connect. I'm assuming that even if tables have public
privileges granted, that they are not visible to people not granted connect
privileges to the database?
Thanks,
Isaac
On Fri, May 22, 2009 at 12:31 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Isaac Dover <isaacdover@gmail.com> writes:
> >> As far as i can tell,
> >> pg_hba.conf is the only manner in which to prevent users from connecting
> to
> >> other users' databases. I've restricted roles to connecting only using
> >> sameuser:
> >>
> >> host sameuser all 192.168.168.0/24 md5
>
> In recent releases (certainly 8.3) the better approach is probably to
> use CONNECT privilege to grant or deny access. However that does have
> some drawbacks if you intend to let users create their own databases
> --- they have to remember to set the privileges properly on new DBs.
>
> 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-sql@postgresql.org
Cc: isaacdover@gmail.com
Subject: Re: help with pg_hba.conf
In-Reply-To: <b560e3300905221039r4c8cc072o3dfb54c5a6a9509f@mail.gmail.com>
* 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