From: | Michael Renner <michael(dot)renner(at)amd(dot)co(dot)at> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #5103: "pg_ctl -w (re)start" fails with custom unix_socket_directory |
Date: | 2009-10-08 19:45:53 |
Message-ID: | 4ACE4171.5050205@amd.co.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Federico Aguirre | 2009-10-08 21:35:59 | Re: BUG #5096: Error installing edb_apachephp.bin |
Previous Message | Alvaro Herrera | 2009-10-08 19:36:37 | Re: BUG #5103: "pg_ctl -w (re)start" fails with custom unix_socket_directory |