Tom Lane wrote: > Bruce Momjian <br...@momjian.us> writes: > > Tom Lane wrote: > >> My current feeling about it is that setting unix_socket_directory as a > >> configuration parameter is only useful to those who are deliberately > >> trying to hide their postmaster from regular clients, in which case > >> the fact that pg_ctl -w fails could be seen as a feature not a bug. > >> The way to make it work is of course the same as for any other > >> client, eg put PGHOST=/socket/directory in your environment. > > > Is this current TODO item incorrect? Should it be removed? > > > Have pg_ctl look at PGHOST in case it is a socket directory? > > I dunno why that's there, but it sure *looks* like it's clueless > about the actual behavior of pg_ctl ...
Thanks, removed. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
