BUG #18842: Wrong state in pg_stat_replication? - Mailing list pgsql-bugs

From PG Bug reporting form
Subject BUG #18842: Wrong state in pg_stat_replication?
Date
Msg-id 18842-cd1fbe9c5022eb54@postgresql.org
Whole thread Raw
List pgsql-bugs
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?


pgsql-bugs by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string
Next
From: PG Bug reporting form
Date:
Subject: BUG #18843: ERROR: Input of anonymous composite types is not implemented in array_agg function