Rich Shepard <[EMAIL PROTECTED]> writes:
> Is there a method other than a reboot to remedy this?
Stop the postmaster, remove the bogus socket file by hand, start the
postmaster.
I imagine that if you check the postmaster log you will notice a bleat
near the beginning about failing to open the socket file (because of
the pre-existence of the root-owned file). It would come up anyway as
long as it could establish a TCP listen socket.
Offhand I would guess that things got this way because of some errant
tmp-cleaning script; perhaps the socket file got chown'd to root
sometime in the past during the previous postmaster's life.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
