On Mon, Dec 18, 2017 at 12:14 PM, Robert Haas <robertmh...@gmail.com> wrote: > On Thu, Dec 14, 2017 at 7:51 PM, Masahiko Sawada <sawada.m...@gmail.com> > wrote: >> +1 from me. > > Works for me, too, although I still don't really follow how it's > happening in the present coding.
Craig has mentioned at least one way upthread: https://www.postgresql.org/message-id/CAMsr+YHj4asAu8dJ1Q5hiW+wxL2Jd1=uxo52dvxhmxive-x...@mail.gmail.com And that's possible when building with LOCK_DEBUG with trace_lwlocks enabled at least. So I would rather not rely on assuming that CHECK_FOR_INTERRUPTS() as a code path never taken for the cases discussed here. -- Michael
