Re: BUG #5103: "pg_ctl -w (re)start" fails with custom unix_socket_directory
От | Alvaro Herrera |
---|---|
Тема | Re: BUG #5103: "pg_ctl -w (re)start" fails with custom unix_socket_directory |
Дата | |
Msg-id | 20091008004551.GQ7719@alvh.no-ip.org обсуждение исходный текст |
Ответ на | BUG #5103: "pg_ctl -w (re)start" fails with custom unix_socket_directory ("Michael Renner" <michael.renner@amd.co.at>) |
Ответы |
Re: BUG #5103: "pg_ctl -w (re)start" fails with custom unix_socket_directory
|
Список | 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.
В списке pgsql-bugs по дате отправления: