Closed Raphyyy closed 6 years ago
There was a bug in Pgpool-II 3.7.2 when primary node is not node 0. We reverted the commit that caused this bug and released a update version 3.7.2-2.
Could you try the latest release 3.7.2-2? pgpool-II-pgxx-3.7.2-2pgdg.rhel7.x86_64.rpm
Download from here: http://www.pgpool.net/yum/rpms/3.7/redhat/rhel-7-x86_64/
Indeed, issue solved with latest source (https://git.postgresql.org/gitweb/?p=pgpool2.git;a=snapshot;h=af4ea10d139a7471ee912140e5f44a0d085bee44;sf=tgz)
Hi and thanks for your work.
I use pgpool2 3.7.2 with 2 backend as master-slave mode with native stream replication.
I think I have an issue whenever I do these steps :
Here is pgpool log which demonstrate well the weird behaviour :
The primary node is node 1, however it send INSERT on the standby. If I shut node 0, INSERT are sent to node 1 just well. If I restart node 0, the problem shows up again.
With select pg_is_in_recovery(); and pcp_node_info I can see that node 1 is the master and node 0 is the standby.
I can manually INSERT on Node 1 directly. On Node 0, I have the same error as expected : cannot execute INSERT in a read-only transaction
With log_error_verbosity = verbose I have no revelant information.
Here is my pgpool.conf :
pgpool.conf.txt