Re: Bug with pg_ctl -w/wait and config-only directories
От | Bruce Momjian |
---|---|
Тема | Re: Bug with pg_ctl -w/wait and config-only directories |
Дата | |
Msg-id | 201110042118.p94LI5k05974@momjian.us обсуждение исходный текст |
Ответ на | Re: Bug with pg_ctl -w/wait and config-only directories (Greg Stark <stark@mit.edu>) |
Ответы |
Re: Bug with pg_ctl -w/wait and config-only directories
|
Список | pgsql-hackers |
Greg Stark wrote: > On Tue, Oct 4, 2011 at 2:42 PM, Bruce Momjian <bruce@momjian.us> wrote: > > Because pg_ctl 9.1 will read postmaster.pid and find the port number, > > socket location, and listen host for wait mode --- I doubt someone would > > do that work in a script. > > But this is the whole difference between them. An init.d script > *shouldn't* do all that. It *knows* how the system daemon is > configured and should only be used to start and stop that process. And > it can't wait, it's not an interactive tool, it has to implement the > standard init.d interface. > > An interactive tool can dwim automatically but that isn't appropriate > for a startup script. A startupt script should always do the same > thing exactly and do that based on the OS policy, not based on > inspecting what programs are actually running on the machine. I agree, except the Gentoo script does exactly that --- wait for completion using pg_ctl -w. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +
В списке pgsql-hackers по дате отправления: