Re: hung backends stuck in spinlock heavy endless loop

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: hung backends stuck in spinlock heavy endless loop
Дата
Msg-id 21866.1421248412@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: hung backends stuck in spinlock heavy endless loop  (Merlin Moncure <mmoncure@gmail.com>)
Ответы Re: hung backends stuck in spinlock heavy endless loop  (Andres Freund <andres@2ndquadrant.com>)
Список 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 по дате отправления:

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: hung backends stuck in spinlock heavy endless loop
Следующее
От: Andres Freund
Дата:
Сообщение: Re: hung backends stuck in spinlock heavy endless loop