Re: BUG #5103: "pg_ctl -w (re)start" fails with custom unix_socket_directory - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #5103: "pg_ctl -w (re)start" fails with custom unix_socket_directory
Date
Msg-id 5165.1255142106@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #5103: "pg_ctl -w (re)start" fails with custom unix_socket_directory  (Bruce Momjian <bruce@momjian.us>)
Responses Re: BUG #5103: "pg_ctl -w (re)start" fails with custom unix_socket_directory
List pgsql-bugs
Bruce Momjian <bruce@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 ...

            regards, tom lane

pgsql-bugs by date:

Previous
From: Federico Aguirre
Date:
Subject: Re: BUG #5096: Error installing edb_apachephp.bin
Next
From: Bruce Momjian
Date:
Subject: Re: BUG #5103: "pg_ctl -w (re)start" fails with custom unix_socket_directory