From: Tomas Vondra <tomas.vondra@enterprisedb.com>
To: depesz@depesz.com, pgsql-bugs mailing list <pgsql-bugs@postgresql.org>
Subject: Re: Backend handling replication slot stuck using 100% cpu, unkillable
Date: Tue, 4 Jul 2023 13:30:21 +0200
Message-ID: <b30f3919-6181-cbf9-4011-e6fb374dba91@enterprisedb.com> (raw)
In-Reply-To: <ZKLF3zT4kV+VUGjJ@depesz.com>
References: <ZKKywNsS9tR/3R80@depesz.com>
<ZKLF3zT4kV+VUGjJ@depesz.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tomas.vondra@enterprisedb.com
Subject: Re: Backend handling replication slot stuck using 100% cpu, unkillable
In-Reply-To: <b30f3919-6181-cbf9-4011-e6fb374dba91@enterprisedb.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox