Re: Backend handling replication slot stuck using 100% cpu, unkillable

Поиск
Список
Период
Сортировка
От Tomas Vondra
Тема Re: Backend handling replication slot stuck using 100% cpu, unkillable
Дата
Msg-id b30f3919-6181-cbf9-4011-e6fb374dba91@enterprisedb.com
обсуждение исходный текст
Ответ на Re: Backend handling replication slot stuck using 100% cpu, unkillable  (hubert depesz lubaczewski <depesz@depesz.com>)
Ответы Re: Backend handling replication slot stuck using 100% cpu, unkillable  (hubert depesz lubaczewski <depesz@depesz.com>)
Список pgsql-bugs
On 7/3/23 14:58, hubert depesz lubaczewski wrote:
> ...
> 
> and then it went back to hash_seq_search  :(
>

So is it an infinite loop in ReorderBufferExecuteInvalidations, or is it
just the case that there are many invalidations? I can't really deduce
that from the backtraces.

How many invalidations does the transaction have? Should be enough to

  print txn->ninvalidations

Also, is there anything interesting about the transaction? You know the
XID (2741814901) so maybe use pg_waldump to see what it did.


regards

-- 
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



В списке pgsql-bugs по дате отправления:

Предыдущее
От: PG Bug reporting form
Дата:
Сообщение: BUG #18014: Releasing catcache entries makes schema_to_xmlschema() fail when parallel workers are used
Следующее
От: hubert depesz lubaczewski
Дата:
Сообщение: Re: Backend handling replication slot stuck using 100% cpu, unkillable