Re: Patch BUG #5103: "pg_ctl -w (re)start" fails with custom unix_socket_directory
От | Alvaro Herrera |
---|---|
Тема | Re: Patch BUG #5103: "pg_ctl -w (re)start" fails with custom unix_socket_directory |
Дата | |
Msg-id | 1291037103-sup-2172@alvh.no-ip.org обсуждение исходный текст |
Ответ на | Patch BUG #5103: "pg_ctl -w (re)start" fails with custom unix_socket_directory (Quan Zongliang <quanzongliang@gmail.com>) |
Ответы |
Re: Patch BUG #5103: "pg_ctl -w (re)start" fails with
custom unix_socket_directory
|
Список | pgsql-hackers |
Excerpts from Quan Zongliang's message of sáb nov 27 06:03:12 -0300 2010: > Hi, all > > I created a pg_ctl patch to fix: > * BUG #5103: "pg_ctl -w (re)start" fails with custom unix_socket_directory > Allow pg_ctl to work properly with configuration files located outside the PGDATA directory I think the way this should work is that you call postmaster with a new switch and it prints out its configuration, after reading the appropriate config file(s). That way it handles all the little details such as figuring out the correct config file, hadle include files, etc. This output would be presumably easier to parse and more trustworthy. Right now we have --describe-config, which is missing the values for each config option. -- Álvaro Herrera <alvherre@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support
В списке pgsql-hackers по дате отправления: