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

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

Thanks, removed.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #5103: "pg_ctl -w (re)start" fails with custom unix_socket_directory
Next
From: "Balazs Klein"
Date:
Subject: BUG #5108: plpgsql function name conflict with table alias