Re: "stuck spinlock" - Mailing list pgsql-hackers

From Tom Lane
Subject Re: "stuck spinlock"
Date
Msg-id 9157.1386948648@sss.pgh.pa.us
Whole thread Raw
In response to Re: "stuck spinlock"  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: "stuck spinlock"
List pgsql-hackers
Andres Freund <andres@2ndquadrant.com> writes:
> On 2013-12-13 09:52:06 -0500, Tom Lane wrote:
>> I think you're probably right:
>> what should be in the interrupt handler is something like
>> "if (ImmediateInterruptOK) CHECK_FOR_INTERRUPTS();"

> Yea, that sounds right. Or just don't set process interrupts there, it
> doesn't seem to be required for correctness?

It is if we need to break out of a wait-for-lock ...
        regards, tom lane



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: "stuck spinlock"
Next
From: Andres Freund
Date:
Subject: Re: "stuck spinlock"