I think that permissions on the parent directories can result in this
error.
Carol
On Jun 26, 2009, at 1:07 PM, Kevin Grittner wrote:
Andy Shellam <andy-lists@xxxxxxxxxxxxxx> wrote:
donghe@xxxxxxxxxxx wrote:
Unable to connect to PostgreSQL server:
could not connect to server: Permission denied
Is the server running on host "localhost" and accepting
TCP/IP connections on port 5432? "
Because the error is "Permission denied", I'm guessing it's
permissions on the /tmp/.s.PGSQL.5432 socket that will need
checking?
If it was trying to get that sort of connection, rather than TCP/IP,
the message would be different. Something like:
# could not connect to server: No such file or directory
# Is the server running locally and accepting
# connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
You do have a point on the "Permission denied", though. If the
problem was where I was suggesting, it would probably say "Connection
refused". Perhaps some OS security restriction is in play here.
-Kevin
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
