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

2010-02-23 Thread Michael Renner
On 22.02.2010 23:38, Bruce Momjian wrote: Michael Renner wrote: 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

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

2009-10-08 Thread Michael Renner
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

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

2009-10-08 Thread Michael Renner
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

[BUGS] BUG #5103: pg_ctl -w (re)start fails with custom unix_socket_directory

2009-10-07 Thread Michael Renner
The following bug has been logged online: Bug reference: 5103 Logged by: Michael Renner Email address: michael.ren...@amd.co.at PostgreSQL version: HEAD Operating system: Linux Description:pg_ctl -w (re)start fails with custom unix_socket_directory Details: When