Marko Kreen <markokr@xxxxxxxxx> writes: > You talked about blocking in quickdie(), but you'd need > to block in elog(). I'm not really particularly worried about that case. By that logic, we could not use quickdie at all, because any part of the system might be doing something that wouldn't survive being interrupted. In practice the code path isn't sufficiently used or critical enough to be worth trying to make that bulletproof. It does strike me that we might someday add code to the postmaster to SIGKILL processes that fail to exit in a reasonably prompt fashion after SIGQUIT, on the theory that they might be stuck in something like this. But for now, I'm more interested in a one-line fix that will deal with the actually observed case ... regards, tom lane -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
