[pgpool-general: 9054] Re: 0 th backend is not valid after upgrading to 4.5.1

[Tatsuo Ishii]

> Hi,
> 
> After upgrading from 4.5.0 to 4.5.1 we see lots of regressions in our
> test-suite when failovers are involved with the following exception in
> WildFly:
> Caused by: org.postgresql.util.PSQLException: ERROR: unable to read message
> kind from backend
>   Detail: 0 th backend is not valid
> 
> I'm not sure what is causing this, but I've got the feeling that pgpool
> keeps trying to send queries to a database that not available. I've
> attached logging from pgpool. You can find the first error at 04:10:16
> (or 2024-03-27T03:10:16.735933246Z pgpool timestamp).

Can you share the backend status information at 04:10:16?
- Each backend node id status (up or down)
- Which was the primary node id?

Best reagards,
--
Tatsuo Ishii
SRA OSS LLC
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp