Yups, which is why I described your problem as non-existent in my previous message. If you tried to connect to the database server you'd see this for yourself.
Another way to check for this would be to use service postgresql status (or onestatus), sockstat -4l which would list the daemon listening on localhost and of course pg_ctl status but that only works when logged on as the UID which owns the actual database process.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.