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. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
