public inbox for [email protected]
help / color / mirror / Atom feedFrom: Luca Ferrari <[email protected]>
To: [email protected]
Subject: what is causing different pcp_node_info status
Date: Fri, 17 Oct 2025 12:45:16 +0200
Message-ID: <CAKoxK+6mkk5r3WREDUduu-ZQH0S87x=cddYDMDyvYyfTzDxj1w@mail.gmail.com> (raw)
Hi all,
I'm using PgPool 4.6.2, PostgreSQL 17.5, three nodes:
- pg1 primary
- pg2 replica
- pg3 replica
So far so good, the initial situation of pcp_node_info reported by all
the nodes seems consistent:
% ssh pg1 'sudo -u postgres pcp_node_info -U pgpool'
pg1 5432 2 0.166667 up up primary primary 0 none none 2025-10-16 11:49:45
pg2 5432 2 0.333333 up up standby standby 0 streaming async 2025-10-16 12:02:10
pg3 5432 2 0.500000 up up standby standby 0 streaming async 2025-10-16 11:49:53
% ssh pg2 'sudo -u postgres pcp_node_info -U pgpool'
pg1 5432 1 0.166667 waiting up primary primary 0 none none 2025-10-16 11:51:36
pg2 5432 1 0.333333 waiting up standby standby 0 streaming async
2025-10-16 12:02:09
pg3 5432 1 0.500000 waiting up standby standby 0 streaming async
2025-10-16 11:51:36
% ssh pg3 'sudo -u postgres pcp_node_info -U pgpool'
pg1 5432 1 0.166667 waiting up primary primary 0 none none 2025-10-16 11:41:22
pg2 5432 1 0.333333 waiting up standby standby 0 streaming async
2025-10-16 12:02:09
pg3 5432 1 0.500000 waiting up standby standby 0 streaming async
2025-10-16 11:49:53
Replicas are streaming, so I reboot pg3 (at 17:30) and the situation
appears different:
% ssh pg3 'sudo reboot'
reply
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: [email protected]
Cc: [email protected], [email protected]
Subject: Re: what is causing different pcp_node_info status
In-Reply-To: <CAKoxK+6mkk5r3WREDUduu-ZQH0S87x=cddYDMDyvYyfTzDxj1w@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox