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

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Michael Renner <michael(dot)renner(at)amd(dot)co(dot)at>
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:36:37
Message-ID: 20091008193637.GF5510@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.

> 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.

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Renner 2009-10-08 19:45:53 Re: BUG #5103: "pg_ctl -w (re)start" fails with custom unix_socket_directory
Previous Message Michael Renner 2009-10-08 19:32:34 Re: BUG #5103: "pg_ctl -w (re)start" fails with custom unix_socket_directory