[pgpool-general: 5057] Possible bug in streaming replication/load-balancing mode when standby is up but way behind.

David Sisk -X (dsisk - TEKSYSTEMS INC at Cisco) dsisk at cisco.com
Wed Oct 19 03:13:53 JST 2016


In two cases, I've gotten this error from PGPool 3.5.4 (with PostgreSQL 9.5.4) when a hot standby was up and available, but not replicating properly and way behind the primary:

-bash-4.1$ psql -h localhost -U jiralt01 jiralt01
psql: ERROR: unable to read message kind
DETAIL: kind does not match between master(53) slot[1] (45)
-bash-4.1$

What I believe should happen is that PGPool should detach that standby (delay_threshold = 10000000)...instead it blocks anything from connecting, which does NOT lead to the intended high-availability of this SR+LB configuration.

Thanks,
Dave Sisk
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20161018/a759800b/attachment.html>


More information about the pgpool-general mailing list