Hi, On Fri, Jan 30, 2009 at 11:55 PM, Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> wrote: > The startup process now catches SIGTERM, and calls proc_exit() at the next > WAL record. That's what will happen in a fast shutdown. Unexpected death of > the startup process is treated the same as a backend/auxiliary process > crash.
If unexpected death of the startup process happens in automatic recovery after a crash, postmaster and bgwriter may get stuck. Because HandleChildCrash() can be called before FatalError flag is reset. When FatalError is false, HandleChildCrash() doesn't kill any auxiliary processes. So, bgwriter survives the crash and postmaster waits for the death of bgwriter forever with recovery status (which means that new connection cannot be started). Is this bug? Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
