| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(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-10 02:35:06 |
| Message-ID: | 5165.1255142106@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> 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?
I dunno why that's there, but it sure *looks* like it's clueless
about the actual behavior of pg_ctl ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2009-10-10 10:08:49 | Re: BUG #5103: "pg_ctl -w (re)start" fails with custom unix_socket_directory |
| Previous Message | Federico Aguirre | 2009-10-10 00:35:14 | Re: BUG #5096: Error installing edb_apachephp.bin |