Re: hung backends stuck in spinlock heavy endless loop - Mailing list pgsql-hackers

From Tom Lane
Subject Re: hung backends stuck in spinlock heavy endless loop
Date
Msg-id 21866.1421248412@sss.pgh.pa.us
Whole thread Raw
In response to Re: hung backends stuck in spinlock heavy endless loop  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: hung backends stuck in spinlock heavy endless loop
List pgsql-hackers
Merlin Moncure <mmoncure@gmail.com> writes:
> Yes, it is pg_class is coming from  LockBufferForCleanup ().  As you
> can see above, it has a shorter runtime.   So it was killed off once
> about a half hour ago which did not free up the logjam.  However, AV
> spawned it again and now it does not respond to cancel.

Interesting.  That seems like there might be two separate issues at
play.  It's plausible that LockBufferForCleanup might be interfering
with other attempts to scan the index, but then why wouldn't killing
the AV have unstuck things?

Anyway it's now seeming that Peter may have the right idea about
where to look.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: hung backends stuck in spinlock heavy endless loop
Next
From: Andres Freund
Date:
Subject: Re: hung backends stuck in spinlock heavy endless loop