On Wed, Nov 26, 2014 at 7:13 PM, Jeff Janes <jeff.ja...@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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers