From the thread so far it seems you're concerned that a process group gets SIGKILLed by default when the process group leader exits. That's certainly a significant change, but I'm not sure I see scenarios in which it should lead to data loss.
I work a lot with PostgreSQL, and in the case of it or any other properly functioning RDBMS what systemd is doing is actually quite useful. In PostgreSQL if the postmaster crashes out (which it shouldn't, but with memory errors, etc, it may) it needs a way to terminate its child processes in a timely and reliable way before the postmaster can be relaunched.
Having systemd do that automatically would actually be quite handy, to the point where on systemd-based systems I wonder if the postmaster shouldn't attempt to auto-restart its self like it usually does, and should instead exit. That way systemd would clean up its children then relaunch it.
Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds