On Jun13, 2012, at 15:14 , Honza Horak wrote: > Since systemd with it's PrivateTmp feature is going to be used in more and > more distros, there will probably be a bigger need to solve in-accessible > default unix socket directory /tmp in the future. > > Thus, I'd like to ask if anybody is aware of any issue connected with simply > patching pg_config_manual.h, same as Debian does it already? For example, is > there any piece of software, that simply rely on /tmp location of the socket > and doesn't use libpg for the communication?
I've used self-compiled postgres version on debian for years, and debian's way of doing things is major PITA in that situation. You end up having to specify that full path to the socket directory *everywhere*, because otherwise things start to break if you recompile something and it suddenly happens to use the debian-supplied libpq instead of your own. Supporting sockets in multiple directories would solve that, once and for all. best regards, Florian Pflug -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
