Re: pg_ctl -w vs unix_socket_directory - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_ctl -w vs unix_socket_directory
Date
Msg-id 11786.1190157231@sss.pgh.pa.us
Whole thread Raw
In response to pg_ctl -w vs unix_socket_directory  (Radoslaw Zielinski <radek42@gmail.com>)
Responses Re: pg_ctl -w vs unix_socket_directory
Re: pg_ctl -w vs unix_socket_directory
List pgsql-hackers
Radoslaw Zielinski <radek42@gmail.com> 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 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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Radoslaw Zielinski
Date:
Subject: Re: pg_ctl -w vs unix_socket_directory
Next
From: Andrew Dunstan
Date:
Subject: Re: pg_ctl -w vs unix_socket_directory