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

From Michael Renner
Subject Re: BUG #5103: "pg_ctl -w (re)start" fails with custom unix_socket_directory
Date
Msg-id 4ACE4171.5050205@amd.co.at
Whole thread Raw
In response to Re: BUG #5103: "pg_ctl -w (re)start" fails with custom unix_socket_directory  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: BUG #5103: "pg_ctl -w (re)start" fails with custom unix_socket_directory
List pgsql-bugs
Alvaro Herrera wrote:
> Michael Renner wrote:
>
>> Mentioning PGHOST in pg_ctl's
>> manpage/documentation should make this entirely clear for people who
>> aren't familiar with the extensive environment variables PostgreSQLs
>> client library can use. [1]
>
> Yeah, this has been complained about many, many times.

Usually an indicator that it need's fixing, eh? ;)

>> If this is a viable option I can write a small patch against the
>> documentation.
>
> I think the patch we need here is something that creates a separate
> manpage for the libpq environment variables, and some kind of note in
> each and every libpq-using program referring the user to that page.

Looking through the available variables probably only PGHOST seems to be
of interest for pg_ctl's purposes; psql's manpage already refers to The
Documentation for further variables and information. What's needed in
pg_ctl's case is just a pointer for the uninformed, at least for me
that'd have sufficed.

best regards,
Michael

pgsql-bugs by date:

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