| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | zxwsbg12138(at)gmail(dot)com |
| Subject: | BUG #18842: Wrong state in pg_stat_replication? |
| Date: | 2025-03-13 08:45:54 |
| Message-ID: | 18842-cd1fbe9c5022eb54@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 18842
Logged by: Bowen Shi
Email address: zxwsbg12138(at)gmail(dot)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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Devrim Gündüz | 2025-03-13 10:08:13 | Re: BUG #18833: libpq.so doesn't contain declared symbol in rpm --provides |
| Previous Message | Masahiko Sawada | 2025-03-13 08:14:11 | Re: BUG #18828: Crash when pg_get_logical_snapshot_meta() passed empty string |