Re: "stuck spinlock"

Hi,

On 2013-12-12 19:35:36 -0800, Christophe Pettus wrote:
> On Dec 12, 2013, at 6:41 PM, Andres Freund <andres@2ndquadrant.com> wrote:
> 
> > Christophe: are there any "unusual" ERROR messages preceding the crash,
> > possibly some minutes before?
> 
> Interestingly, each spinlock PANIC is *followed*, about one minute later (+/- five seconds) by a "canceling statement
dueto statement timeout" on that exact query.  The queries vary enough in text that it is unlikely to be a
coincidence.
> 
> There are a *lot* of "canceling statement due to statement timeout" messages, which is interesting, because:

Tom, could this be caused by c357be2cd9434c70904d871d9b96828b31a50cc5?
Specifically the added CHECK_FOR_INTERRUPTS() in handle_sig_alarm()?
ISTM nothing is preventing us from jumping out of code holding a
spinlock?

Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services