From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: zxwsbg12138@gmail.com
Subject: BUG #18842: Wrong state in pg_stat_replication?
Date: Thu, 13 Mar 2025 08:45:54 +0000
Message-ID: <18842-cd1fbe9c5022eb54@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 18842
Logged by: Bowen Shi
Email address: zxwsbg12138@gmail.com
PostgreSQL version: 15.6
Operating system: centos
Description:
Hi dears,
I recently discovered that when the primary->standby connection fails (I'm
afraid I'm not sure about the cause of the primary-standby interruption, it
is likely due to WAL forking.). The state of pg_stat_replication cycles
continuously from
walsender process start -> catchup -> streaming -> walsender process exit.
And the walsender process only existed in less than 1 second. I would like
to know if anyone has encountered a similar scenario before? And do we have
any discussion about this?
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: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, zxwsbg12138@gmail.com
Subject: Re: BUG #18842: Wrong state in pg_stat_replication?
In-Reply-To: <18842-cd1fbe9c5022eb54@postgresql.org>
* 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