Postgres Pro
Downloads
Home   >   mailing lists

Re: Backend handling replication slot stuck using 100% cpu, unkillable - Mailing list pgsql-bugs

From Tomas Vondra
Subject Re: Backend handling replication slot stuck using 100% cpu, unkillable
Date
Msg-id b30f3919-6181-cbf9-4011-e6fb374dba91@enterprisedb.com
Whole thread Raw
In response to Re: Backend handling replication slot stuck using 100% cpu, unkillable  (hubert depesz lubaczewski <depesz@depesz.com>)
Responses Re: Backend handling replication slot stuck using 100% cpu, unkillable
List pgsql-bugs
Tree view 
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 by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #18014: Releasing catcache entries makes schema_to_xmlschema() fail when parallel workers are used
Next
From: hubert depesz lubaczewski
Date:
Subject: Re: Backend handling replication slot stuck using 100% cpu, unkillable