pg_ctl -w vs unix_socket_directory

Поиск
Список
Период
Сортировка
От Radoslaw Zielinski
Тема pg_ctl -w vs unix_socket_directory
Дата
Msg-id 20070918222454.GA14278@bzium
обсуждение исходный текст
Ответы Re: pg_ctl -w vs unix_socket_directory  (Andrew Dunstan <andrew@dunslane.net>)
Re: pg_ctl -w vs unix_socket_directory  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Дерево обсуждения 
Hello,

"pg_ctl -w -D ... start" doesn't work when unix_socket_directory is set
to somewhere else than the compiled in default ("/tmp").  Having this is
useful for the startup scripts, so the status "DONE" actually means
success, instead of "maybe".

Jeff Davis wrote about it a while ago:
http://svr5.postgresql.org/pgsql-general/2006-09/msg01141.php


Simple hacky patch for v8.2.5; maybe someone finds it useful before
the proper config parser is integrated:
http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/postgresql-pg_ctl-fix.patch?rev=HEAD

--
Radosław Zieliński <radek@pld-linux.org>

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter
Следующее
От: Andrew Dunstan
Дата:
Сообщение: Re: [COMMITTERS] pgsql: Close previously open holes for invalidly encoded data to enter