Re: Ah, yet another cause for not binding the right port....

Steve Wolfe wrote:
>    When postgres binds to any port, it likes to write a file in /tmp, along
> the lines of ".s.PGSQL.5432".  If /tmp is not writeable by the postgres

Just in case you missed it, that file in /tmp is not a real file, but
a "socket" (Unix domain).

> process, it will not be able to bind to any port.  However, it doesn't give
> you an intelligent error message like "Can't create file", it simply says
> that it can't bind the port, and of course, asks if another postgres
> process is already running.

If the node is there, it can't "bind" to the "port". Ofcourse, you
just delete it to mix it :)
-- 
Martijn van Oosterhout <kleptog@cupid.suninternet.com>
http://cupid.suninternet.com/~kleptog/