> 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"?
>
Ah yeah, good point.
>
> 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.
>
SELinux? I've never used it personally but have heard it can throw some
errors you don't normally expect.