Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> Unless ImmediateInterruptOK is set, but it's only set around a few
> blocking system calls where it is safe to do so. (Checks...) Actually,
> md5_crypt_verify() looks suspicious, it does "ImmediateInterruptOK =
> true", and then calls palloc() and pfree().
Hm, yeah, and ClientAuthentication() seems way too optimistic about what
it does with that set too. I'm not sure what we can do about it though.
The general shape of the problem here is that we're about to go off into
uncooperative third-party libraries like krb5, so if we don't enable
interrupts we're going to have problems honoring authentication timeout.
regards, tom lane
