Whoops! I believe this issue has been fixed in postgresql-common, although I had to edit the cluster configuration to comment the socket path.

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to