I don't quite understand this bug report, to be honest. If you change
the server's socket dir (to e. g. /tmp, which is _highly_ discouraged,
btw!), then of course you have to do the corresponding change to the
client side. libpq-dev, pg-perl, python's DB API, and just about any
other API I know allow you to set the socket path.
By default, server and client use /var/run/postgresql/, which should
work just fine. Can you please explain in more detail what the problem
is here? Thank you!
** Changed in: postgresql-8.3 (Ubuntu)
Status: New => Incomplete
--
server upgrade should warn about non standard socket dir
https://bugs.launchpad.net/bugs/351497
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs