| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Michael Renner <michael(dot)renner(at)amd(dot)co(dot)at> |
| Cc: | 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 00:45:51 |
| Message-ID: | 20091008004551.GQ7719@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Michael Renner wrote:
> When using a non-standard unix_socket_directory setting, pg_ctl -w (re)start
> fails because it checks for the socket file to appear in it's default
> location.
Yeah, this has been discussed before. It's been suggested that pg_ctl
should parse postgresql.conf to figure out the settings, but no one has
gotten around to it. Feel free to give it a whirl if you're so inclined.
Hmm, another idea would be to have a new postmaster switch that would
report the value of any given configuration option. So pg_ctl wouldn't
have to get into the business of parsing the config file, but would
simply ask postmaster for the value (which already knows how to parse
the file).
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-10-08 03:03:24 | Re: BUG #5103: "pg_ctl -w (re)start" fails with custom unix_socket_directory |
| Previous Message | Michael Renner | 2009-10-08 00:26:16 | BUG #5103: "pg_ctl -w (re)start" fails with custom unix_socket_directory |