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. ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
