craig@tintri.com writes:
> We found one of our Postgresql processes deadlocked with this backtrace. It
> is not safe to call syslog() in a signal handler on Linux. We are using
> version 8.4.20. I looked at newer versions sourcecode and I believe they
> have the same problem.
Well, the alternatives are to do this or not leave any trace of why the
process exited. Newer versions than 8.4 (which is EOL btw) have an
amelioration mechanism for this and related risks, which is that the
postmaster SIGKILLs any child that doesn't exit within a few seconds.
regards, tom lane
