MIME-Version: 1.0
References: 
 <CAKoxK+6mkk5r3WREDUduu-ZQH0S87x=cddYDMDyvYyfTzDxj1w@mail.gmail.com>
In-Reply-To: 
 <CAKoxK+6mkk5r3WREDUduu-ZQH0S87x=cddYDMDyvYyfTzDxj1w@mail.gmail.com>
From: Luca Ferrari <fluca1978@gmail.com>
Date: Thu, 23 Oct 2025 08:04:50 +0200
Message-ID: 
 <CAKoxK+5+LFK4kk0Xay+9Rs8AYj9we0_M=T9md4HP0+rjZH6=uQ@mail.gmail.com>
Subject: Re: what is causing different pcp_node_info status
To: pgpool-general@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CAKoxK%2B5%2BLFK4kk0Xay%2B9Rs8AYj9we0_M%3DT9md4HP0%2BrjZH6%3DuQ%40mail.gmail.com>
Precedence: bulk

On Fri, Oct 17, 2025 at 12:45=E2=80=AFPM Luca Ferrari <fluca1978@gmail.com>=
 wrote:
> The problem is that the status of pg3 is not consistent: pg1 reports
> as "up up" while other nodes report as "down up".
> Please note that the updtae timestamp are in sync, 17:32:45 and hence
> the updated seems to have been propagated correctly within pgpool.
> Questions are:
> - is it safe right now to execute a pcp_attach_node ?
> - why is the status not consistent? Anything I should look for within the=
 logs?


I am still observing the issue, the best situation I come is all nodes
reported as "up up" when queryed on pg1 (primary) and "waiting up"
when queried from pg2 and pg3.
could it be network latency or a similar issue?

Thanks,
Luca