On Tue, 2007-09-18 at 19:13 -0400, Tom Lane wrote: > Radoslaw Zielinski <[EMAIL PROTECTED]> writes: > > "pg_ctl -w -D ... start" doesn't work when unix_socket_directory is set > > to somewhere else than the compiled in default ("/tmp"). > > pg_ctl not working is going to be the very least of your worries; > pretty much nothing else will either. >
If you mean client applications won't work, that would be expected from such a change to the server configuration. > If you want some other socket directory, I strongly recommend setting > the path to it at compile time so that it's properly wired into libpq. > AFAICS the only value in specifying unix_socket_directory at server > start is if you actually *want* a stealth server that won't be found > by clients without manual intervention. > Those arguments apply almost as well to the server port. The server port is read from the postgresql.conf from pg_ctl, but not the socket directory. It's an annoyance: if you change the default socket directory, you're probably going to break your init script (on FreeBSD you will, because it uses "-w"). I don't think that's the expected result, and it's not intuitive to find the cause of the problem. I think the inconsistency between server port number and socket directory is less than ideal. However, I also don't feel very strongly about it. It's rare, and a there are plenty of workarounds. Regards, Jeff Davis ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings