|
From: Ross G. <ro...@gr...> - 2005-07-04 05:42:14
|
> Local=3DLocal to the Machine. The connection to your database is betwee= n =20 apache > and postgres, therefore it's a local connection > Remote=3DWhen you try to connect remotely to the machine - You'll only=20 need this > if your database is running on a different machine than apache. > If you > connect to a website, apache connects to the database, and that's seen > as a local connection. > > local allows processes on you machine to connect to the postgres=20 database via unix socket > host allows connection via tcp/ip sockets That's what I thought... > Now your rules allow the sql-ledger user to only connect to template1 =20 database, but sql-leder > needs to create new databases for each company (Datasets). If I understand the README correctly, the initial connection to template1 only tests the database, so as a first step, shouldn't I be=20 able to grant access for user: sql-ledger to only template1? > Try changing it to read and restart postgres > local all sql-ledger trust > host all sql-ledger 127.0.0.1/32 trust > > > This is still only local access to your database, and only the > sql-ledger user is allowed. > > if it doesnt work, you can change it to > local all all trust > host all all 127.0.0.1/32 trust > > Which means any user can access any of the databases on the machine =20 locally. I try to keep a tight leash on postgres access, granting only what is=20 needed for each user. However, I tried both of these and got the same=20 result. Does anyone know for sure if the message "Error! Permission denied" is a= n issue with postgres or apache? Thanks for the input. ross gohlke |