Re: 9.2 recovery/startup problems
От | Robert Haas |
---|---|
Тема | Re: 9.2 recovery/startup problems |
Дата | |
Msg-id | CA+TgmoZ=CuSRtrX8=Re8C6=0_DUma0WB3qKKRo4EiyURQ72v4w@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: 9.2 recovery/startup problems (Jeff Janes <jeff.janes@gmail.com>) |
Ответы |
Re: 9.2 recovery/startup problems
|
Список | pgsql-hackers |
On Wed, Nov 26, 2014 at 7:13 PM, Jeff Janes <jeff.janes@gmail.com> wrote: > If I do a pg_ctl stop -mf, then both files go away. If I do a pg_ctl stop > -mi, then neither goes away. It is only with the /sbin/reboot that I get > the fatal combination of _init being gone but the other still present. Eh? That sounds wonky. I mean, reboot normally kills processes with SIGTERM or SIGKILL, in which case I'd expect the outcome to match what you get with pg_ctl stop -mf or pg_ctl stop -mi. The only way I can see that you'd get a different behavior is if you did a hard reboot (like echo b > /proc/sysrq-trigger); if that changes things, then we might have a missing-fsync bug. How is that reboot managing to leave the main fork behind while losing the init fork? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: