This would fix the problem on Unixen with setsid, which
should be pretty much all of them; on any that don't have it,
the behavior doesn't change. Still leaves Windows out in the
cold, but I don't see that we have anything much we can do
about it there --- Windows users will just have to know to
kill the child script process instead of the postmaster.
I haven't really been folliowing this thread. What exactly is it you
want to accomplish (maybe there is a different way to fix it on win32)?
Kill a process along with all it's subprocesses?


Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 13 of 35 | next ›
Discussion Overview
grouppgsql-hackers @
postedNov 17, '06 at 10:03p
activeNov 30, '06 at 9:40p



site design / logo © 2022 Grokbase