From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Michael Renner <michael(dot)renner(at)amd(dot)co(dot)at>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #5103: "pg_ctl -w (re)start" fails with custom unix_socket_directory |
Date: | 2009-10-09 21:45:59 |
Message-ID: | 200910092145.n99Ljxi26767@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Federico Aguirre | 2009-10-10 00:35:14 | Re: BUG #5096: Error installing edb_apachephp.bin |
Previous Message | Peter Eisentraut | 2009-10-09 14:54:52 | Re: BUG #5106: Relationship between two tables |