Peter Eisentraut <peter_e@gmx.net> writes:
> Yeah, on reflection, calling elog in the SIGQUIT handler is just waiting
> for trouble. The call could block for any number of reasons, because
> there is a boatload of functionality that comes with a logging call. In
> the overall scheme of things, you don't really lose much if you just
> delete the call altogether, because in the event that it's called the
> postmaster will already have logged that it is going to kill all
> children. Or there ought to be some kind of alarm that would abort the
> thing if it takes too long.
Well, the point of that call is not to log the event. The point is to
tell the client why it's losing its connection. Admittedly there are
assorted corner cases where that would fail, but it works well enough
often enough that I don't want to just delete the attempt.
regards, tom lane
