| From: | Jon August <jon(at)internection(dot)com> |
|---|---|
| To: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
| Cc: | Chris Ruprecht <chrup999(at)yahoo(dot)com>, PostGreSQL Admin Group <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: user to database restriction? |
| Date: | 2002-02-11 01:14:16 |
| Message-ID: | Pine.LNX.4.21.0202102009100.6758-100000@www.internection.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Ok, it looks like the final argument is used to set up realtionships
between remote unix users to pg users. So wouldn't that mean that
ultimately the user would be able to view any database anyway since
the pg user can view any database? (aside from revoking privs at the
table level)
Is there any means of user to database access restriction?
On Sun, 10 Feb 2002, Stephan Szabo wrote:
> > local all password postgres
> > host all xxx.xxx.xxx.xxx 255.255.255.255 password postgres
> > local shopdb password mark
> > host shopdb xxx.xxx.xxx.xxx 255.255.255.255 password mark
>
> The final argument goes to an external file in $PGDATA that lists users
> (and optionally passwords) for the users that are allowed into the db.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-02-11 01:43:16 | Re: restore whoes |
| Previous Message | Stephan Szabo | 2002-02-11 01:03:27 | Re: user to database restriction? |