View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000813Pgpool-IIBugpublic2023-09-28 18:202023-10-03 16:33
ReporterphilB Assigned Topengbo  
PrioritynormalSeveritymajorReproducibilityhave not tried
Status assignedResolutionopen 
PlatformLinux 64bitsOSCentOSOS Version7.9
Product Version4.4.4 
Summary0000813: invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
Descriptionafter crash of the primary PostgreSQL server in a 3-nodes Patroni configuration , Pgpool-II did not succeed in finding another primary node
Steps To Reproduce1/ poweroff of a primary postgresql server with 2 standbys
2/ patroni successfully failovers to a new primary
2/ pgpool-II (configured with 3 backends) does not manage to find the new primary backend.
Pgpool-II is in streaming_replication mode.
No load balancing, health check is on
Additional Informationpostgres=# show pool_nodes;
 node_id | hostname | port | status | pg_status | lb_weight | role | pg_role | select_cnt | load_balance_node | replication_delay | replication_state | replication_sync_state | last_status_change
---------+---------------+------+--------+-----------+-----------+---------+---------+------------+-------------------+-------------------+-------------------+------------------------+---------------------
 0 | servdbmopp001 | 5432 | up | up | 0.333333 | primary | standby | 8124 | true | 0 | | | 2023-09-02 03:28:16
 1 | servdbmopp011 | 5432 | up | up | 0.333333 | standby | standby | 0 | false | 0.771517 second | | | 2023-09-02 03:28:16
 2 | servdbmopp021 | 5432 | up | up | 0.333333 | standby | primary | 0 | false | 0.133560 second | | | 2023-09-02 03:28:16

We see that node 0 remains "primary" for Pgpool whereas it is "standby" in Patroni configuration. The primary backend for Pgpool should be node 2.
TagsNo tags attached.

Activities

philB

2023-09-28 18:20

reporter  

pgpool-TueNEW.log (79,420 bytes)    
2023-09-26 15:24:29.379: main pid 1156: LOG:  reaper handler: exiting normally
2023-09-26 15:24:29.433: main pid 1156: LOG:  reaper handler
2023-09-26 15:24:29.434: main pid 1156: LOG:  reaper handler: exiting normally
2023-09-26 15:24:37.313: main pid 1156: LOG:  reaper handler
2023-09-26 15:24:37.314: main pid 1156: LOG:  reaper handler: exiting normally
2023-09-26 15:24:39.443: main pid 1156: LOG:  reaper handler
2023-09-26 15:24:39.444: main pid 1156: LOG:  reaper handler: exiting normally
2023-09-26 15:24:47.921: [unknown] pid 76610: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:47.921: [unknown] pid 76610: DETAIL:  timed out. retrying...
2023-09-26 15:24:49.155: health_check0 pid 1968: LOG:  failed to connect to PostgreSQL server on "servdbmopp001:5432", timed out
2023-09-26 15:24:49.155: health_check0 pid 1968: LOG:  health check retrying on DB node: 0 (round:1)
2023-09-26 15:24:50.390: [unknown] pid 81085: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:50.390: [unknown] pid 81085: DETAIL:  timed out. retrying...
2023-09-26 15:24:50.791: [unknown] pid 77111: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:50.791: [unknown] pid 77111: DETAIL:  timed out. retrying...
2023-09-26 15:24:50.995: [unknown] pid 77951: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:50.995: [unknown] pid 77951: DETAIL:  timed out. retrying...
2023-09-26 15:24:51.395: child pid 89812: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:51.395: child pid 89812: DETAIL:  timed out. retrying...
2023-09-26 15:24:51.465: [unknown] pid 78977: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:51.465: [unknown] pid 78977: DETAIL:  timed out. retrying...
2023-09-26 15:24:52.265: [unknown] pid 69048: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:52.265: [unknown] pid 69048: DETAIL:  timed out. retrying...
2023-09-26 15:24:52.420: child pid 89822: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:52.420: child pid 89822: DETAIL:  timed out. retrying...
2023-09-26 15:24:52.588: [unknown] pid 76366: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:52.588: [unknown] pid 76366: DETAIL:  timed out. retrying...
2023-09-26 15:24:52.845: [unknown] pid 87565: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:52.845: [unknown] pid 87565: DETAIL:  timed out. retrying...
2023-09-26 15:24:52.865: child pid 89838: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:52.865: child pid 89838: DETAIL:  timed out. retrying...
2023-09-26 15:24:53.127: [unknown] pid 77145: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:53.127: [unknown] pid 77145: DETAIL:  timed out. retrying...
2023-09-26 15:24:53.344: [unknown] pid 83999: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:53.344: [unknown] pid 83999: DETAIL:  timed out. retrying...
2023-09-26 15:24:53.348: [unknown] pid 76428: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:53.348: [unknown] pid 76428: DETAIL:  timed out. retrying...
2023-09-26 15:24:54.045: [unknown] pid 77345: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:54.045: [unknown] pid 77345: DETAIL:  timed out. retrying...
2023-09-26 15:24:54.277: [unknown] pid 78066: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:54.277: [unknown] pid 78066: DETAIL:  timed out. retrying...
2023-09-26 15:24:54.345: [unknown] pid 89029: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:54.345: [unknown] pid 89029: DETAIL:  timed out. retrying...
2023-09-26 15:24:54.348: child pid 89741: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:54.348: child pid 89741: DETAIL:  timed out. retrying...
2023-09-26 15:24:54.554: PostgreSQL JDBC Driver pid 75646: LOG:  received degenerate backend request for node_id: 0 from pid [75646]
2023-09-26 15:24:54.554: watchdog pid 1279: LOG:  watchdog received the failover command from local pgpool-II on IPC interface
2023-09-26 15:24:54.554: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from local pgpool-II on IPC interface
2023-09-26 15:24:54.554: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:24:54.554: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:24:54.554: PostgreSQL JDBC Driver pid 75646: LOG:  signal_user1_to_parent_with_reason(0)
2023-09-26 15:24:54.555: PostgreSQL JDBC Driver pid 75646: WARNING:  write on backend 0 failed with error :"Broken pipe"
2023-09-26 15:24:54.555: PostgreSQL JDBC Driver pid 75646: DETAIL:  while trying to write data from offset: 0 wlen: 5
2023-09-26 15:24:54.555: main pid 1156: LOG:  Pgpool-II parent process received SIGUSR1
2023-09-26 15:24:54.555: main pid 1156: LOG:  Pgpool-II parent process has received failover request
2023-09-26 15:24:54.555: watchdog pid 1279: LOG:  received the failover indication from Pgpool-II on IPC interface
2023-09-26 15:24:54.555: watchdog pid 1279: LOG:  watchdog is informed of failover start by the main process
2023-09-26 15:24:54.556: main pid 1156: LOG:  === Starting degeneration. shutdown host servdbmopp001(5432) ===
2023-09-26 15:24:54.558: PostgreSQL JDBC Driver pid 78780: LOG:  received degenerate backend request for node_id: 0 from pid [78780]
2023-09-26 15:24:54.558: watchdog pid 1279: LOG:  watchdog received the failover command from local pgpool-II on IPC interface
2023-09-26 15:24:54.559: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from local pgpool-II on IPC interface
2023-09-26 15:24:54.559: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:24:54.559: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:24:54.562: main pid 1156: LOG:  Restart all children
2023-09-26 15:24:54.564: main pid 1156: LOG:  find_primary_node_repeatedly: waiting for finding a primary node
2023-09-26 15:24:57.170: health_check0 pid 1968: LOG:  failed to connect to PostgreSQL server on "servdbmopp001:5432", getsockopt() failed
2023-09-26 15:24:57.170: health_check0 pid 1968: DETAIL:  Operation now in progress
2023-09-26 15:24:57.170: health_check0 pid 1968: LOG:  health check failed on node 0 (timeout:0)
2023-09-26 15:24:57.170: health_check0 pid 1968: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:24:57.238: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:24:57.238: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:24:57.238: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:24:57.238: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:24:57.238: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:25:01.438: pcp_main pid 41329: LOG:  forked new pcp worker, pid=89910 socket=7
2023-09-26 15:25:01.469: pcp_main pid 41329: LOG:  forked new pcp worker, pid=89913 socket=7
2023-09-26 15:25:01.473: pcp_main pid 41329: LOG:  PCP process with pid: 89913 exit with SUCCESS.
2023-09-26 15:25:01.473: pcp_main pid 41329: LOG:  PCP process with pid: 89913 exits with status 0
2023-09-26 15:25:01.485: pcp_main pid 41329: LOG:  forked new pcp worker, pid=89916 socket=7
2023-09-26 15:25:01.488: pcp_main pid 41329: LOG:  PCP process with pid: 89916 exit with SUCCESS.
2023-09-26 15:25:01.488: pcp_main pid 41329: LOG:  PCP process with pid: 89916 exits with status 0
2023-09-26 15:25:01.496: pcp_main pid 41329: LOG:  forked new pcp worker, pid=89921 socket=7
2023-09-26 15:25:01.499: pcp_main pid 41329: LOG:  forked new pcp worker, pid=89922 socket=7
2023-09-26 15:25:01.501: pcp_main pid 41329: LOG:  PCP process with pid: 89910 exit with SUCCESS.
2023-09-26 15:25:01.502: pcp_main pid 41329: LOG:  PCP process with pid: 89910 exits with status 0
2023-09-26 15:25:01.509: pcp_main pid 41329: LOG:  PCP process with pid: 89921 exit with SUCCESS.
2023-09-26 15:25:01.509: pcp_main pid 41329: LOG:  PCP process with pid: 89921 exits with status 0
2023-09-26 15:25:01.509: pcp_main pid 41329: LOG:  PCP process with pid: 89922 exit with SUCCESS.
2023-09-26 15:25:01.509: pcp_main pid 41329: LOG:  PCP process with pid: 89922 exits with status 0
2023-09-26 15:25:01.511: pcp_main pid 41329: LOG:  forked new pcp worker, pid=89929 socket=7
2023-09-26 15:25:01.520: pcp_main pid 41329: LOG:  forked new pcp worker, pid=89931 socket=7
2023-09-26 15:25:01.525: pcp_main pid 41329: LOG:  PCP process with pid: 89931 exit with SUCCESS.
2023-09-26 15:25:01.526: pcp_main pid 41329: LOG:  PCP process with pid: 89931 exits with status 0
2023-09-26 15:25:01.532: pcp_main pid 41329: LOG:  forked new pcp worker, pid=89932 socket=7
2023-09-26 15:25:01.542: pcp_main pid 41329: LOG:  forked new pcp worker, pid=89933 socket=7
2023-09-26 15:25:01.545: pcp_main pid 41329: LOG:  PCP process with pid: 89933 exit with SUCCESS.
2023-09-26 15:25:01.545: pcp_main pid 41329: LOG:  PCP process with pid: 89933 exits with status 0
2023-09-26 15:25:01.566: pcp_main pid 41329: LOG:  PCP process with pid: 89929 exit with SUCCESS.
2023-09-26 15:25:01.566: pcp_main pid 41329: LOG:  PCP process with pid: 89929 exits with status 0
2023-09-26 15:25:01.593: pcp_main pid 41329: LOG:  PCP process with pid: 89932 exit with SUCCESS.
2023-09-26 15:25:01.593: pcp_main pid 41329: LOG:  PCP process with pid: 89932 exits with status 0
2023-09-26 15:25:01.605: pcp_main pid 41329: LOG:  forked new pcp worker, pid=89939 socket=7
2023-09-26 15:25:01.655: pcp_main pid 41329: LOG:  PCP process with pid: 89939 exit with SUCCESS.
2023-09-26 15:25:01.655: pcp_main pid 41329: LOG:  PCP process with pid: 89939 exits with status 0
2023-09-26 15:25:03.245: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:25:03.245: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:25:03.245: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:25:03.245: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:25:03.245: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:25:09.251: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:25:09.251: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:25:09.251: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:25:09.251: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:25:09.251: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:25:15.257: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:25:15.257: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:25:15.257: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:25:15.257: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:25:15.257: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:25:21.263: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:25:21.263: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:25:21.263: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:25:21.263: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:25:21.263: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:25:27.270: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:25:27.270: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:25:27.270: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:25:27.270: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:25:27.270: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:25:33.275: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:25:33.275: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:25:33.275: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:25:33.275: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:25:33.275: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:25:39.280: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:25:39.281: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:25:39.281: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:25:39.281: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:25:39.281: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:25:45.286: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:25:45.286: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:25:45.286: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:25:45.286: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:25:45.286: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:25:51.295: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:25:51.295: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:25:51.295: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:25:51.295: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:25:51.295: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:25:57.300: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:25:57.300: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:25:57.300: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:25:57.300: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:25:57.300: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:26:03.305: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:26:03.305: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:26:03.305: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:26:03.305: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:26:03.305: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:26:09.310: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:26:09.310: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:26:09.310: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:26:09.310: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:26:09.310: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:26:15.315: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:26:15.315: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:26:15.315: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:26:15.315: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:26:15.315: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:26:21.322: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:26:21.322: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:26:21.322: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:26:21.322: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:26:21.322: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:26:27.328: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:26:27.328: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:26:27.328: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:26:27.328: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:26:27.328: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:26:33.334: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:26:33.334: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:26:33.334: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:26:33.334: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:26:33.334: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:26:39.339: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:26:39.339: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:26:39.339: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:26:39.339: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:26:39.339: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:26:45.346: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:26:45.347: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:26:45.347: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:26:45.347: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:26:45.347: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:26:51.355: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:26:51.355: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:26:51.355: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:26:51.355: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:26:51.355: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:26:57.360: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:26:57.360: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:26:57.361: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:26:57.361: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:26:57.361: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:27:03.366: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:27:03.366: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:27:03.366: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:27:03.366: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:27:03.366: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:27:09.371: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:27:09.371: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:27:09.371: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:27:09.371: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:27:09.371: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:27:15.376: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:27:15.376: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:27:15.376: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:27:15.376: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:27:15.376: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:27:21.387: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:27:21.387: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:27:21.387: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:27:21.387: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:27:21.387: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:27:27.393: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:27:27.393: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:27:27.393: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:27:27.393: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:27:27.393: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:27:33.399: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:27:33.399: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:27:33.400: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:27:33.400: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:27:33.400: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:27:39.405: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:27:39.405: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:27:39.405: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:27:39.405: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:27:39.405: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:27:43.974: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90103 socket=7
2023-09-26 15:27:44.027: pcp_main pid 41329: LOG:  PCP process with pid: 90103 exit with SUCCESS.
2023-09-26 15:27:44.027: pcp_main pid 41329: LOG:  PCP process with pid: 90103 exits with status 0
2023-09-26 15:27:45.412: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:27:45.413: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:27:45.413: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:27:45.413: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:27:45.413: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:27:51.419: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:27:51.419: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:27:51.419: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:27:51.419: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:27:51.419: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:27:57.425: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:27:57.425: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:27:57.425: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:27:57.425: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:27:57.425: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:28:03.430: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:28:03.430: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:28:03.430: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:28:03.430: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:28:03.430: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:28:09.436: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:28:09.436: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:28:09.436: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:28:09.436: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:28:09.436: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:28:15.443: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:28:15.443: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:28:15.443: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:28:15.443: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:28:15.443: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:28:16.502: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:28:16.502: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:28:16.502: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:28:16.502: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:28:16.502: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:28:18.427: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90138 socket=7
2023-09-26 15:28:18.474: pcp_main pid 41329: LOG:  PCP process with pid: 90138 exit with SUCCESS.
2023-09-26 15:28:18.474: pcp_main pid 41329: LOG:  PCP process with pid: 90138 exits with status 0
2023-09-26 15:28:19.536: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:28:19.536: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:28:19.536: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:28:19.536: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:28:19.536: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:28:21.448: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:28:21.448: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:28:21.448: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:28:21.448: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:28:21.448: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:28:27.454: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:28:27.454: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:28:27.454: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:28:27.454: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:28:27.454: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:28:33.459: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:28:33.459: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:28:33.459: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:28:33.459: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:28:33.459: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:28:39.465: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:28:39.465: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:28:39.465: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:28:39.465: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:28:39.465: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:28:45.470: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:28:45.471: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:28:45.471: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:28:45.471: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:28:45.471: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:28:51.479: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:28:51.479: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:28:51.479: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:28:51.479: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:28:51.479: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:28:57.485: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:28:57.485: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:28:57.485: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:28:57.485: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:28:57.485: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:29:03.492: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:29:03.492: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:29:03.492: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:29:03.492: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:29:03.492: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:29:09.498: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:29:09.498: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:29:09.498: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:29:09.498: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:29:09.498: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:29:15.503: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:29:15.503: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:29:15.503: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:29:15.503: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:29:15.503: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:29:21.509: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:29:21.509: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:29:21.509: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:29:21.509: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:29:21.509: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:29:27.514: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:29:27.514: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:29:27.514: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:29:27.514: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:29:27.514: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:29:33.519: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:29:33.520: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:29:33.520: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:29:33.520: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:29:33.520: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:29:39.525: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:29:39.525: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:29:39.525: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:29:39.525: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:29:39.525: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:29:45.534: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:29:45.534: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:29:45.534: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:29:45.534: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:29:45.534: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:29:51.542: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:29:51.542: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:29:51.542: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:29:51.542: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:29:51.542: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:29:57.551: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:29:57.551: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:29:57.551: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:29:57.551: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:29:57.551: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:30:01.680: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90293 socket=7
2023-09-26 15:30:01.695: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90296 socket=7
2023-09-26 15:30:01.697: pcp_main pid 41329: LOG:  PCP process with pid: 90293 exit with SUCCESS.
2023-09-26 15:30:01.697: pcp_main pid 41329: LOG:  PCP process with pid: 90293 exits with status 0
2023-09-26 15:30:01.708: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90300 socket=7
2023-09-26 15:30:01.717: pcp_main pid 41329: LOG:  PCP process with pid: 90300 exit with SUCCESS.
2023-09-26 15:30:01.717: pcp_main pid 41329: LOG:  PCP process with pid: 90300 exits with status 0
2023-09-26 15:30:01.732: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90303 socket=7
2023-09-26 15:30:01.735: pcp_main pid 41329: LOG:  PCP process with pid: 90303 exit with SUCCESS.
2023-09-26 15:30:01.735: pcp_main pid 41329: LOG:  PCP process with pid: 90303 exits with status 0
2023-09-26 15:30:01.749: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90305 socket=7
2023-09-26 15:30:01.752: pcp_main pid 41329: LOG:  PCP process with pid: 90305 exit with SUCCESS.
2023-09-26 15:30:01.752: pcp_main pid 41329: LOG:  PCP process with pid: 90305 exits with status 0
2023-09-26 15:30:01.762: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90308 socket=7
2023-09-26 15:30:01.766: pcp_main pid 41329: LOG:  PCP process with pid: 90308 exit with SUCCESS.
2023-09-26 15:30:01.766: pcp_main pid 41329: LOG:  PCP process with pid: 90308 exits with status 0
2023-09-26 15:30:01.771: pcp_main pid 41329: LOG:  PCP process with pid: 90296 exit with SUCCESS.
2023-09-26 15:30:01.771: pcp_main pid 41329: LOG:  PCP process with pid: 90296 exits with status 0
2023-09-26 15:30:01.777: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90316 socket=7
2023-09-26 15:30:01.780: pcp_main pid 41329: LOG:  PCP process with pid: 90316 exit with SUCCESS.
2023-09-26 15:30:01.780: pcp_main pid 41329: LOG:  PCP process with pid: 90316 exits with status 0
2023-09-26 15:30:01.782: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90320 socket=7
2023-09-26 15:30:01.796: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90322 socket=7
2023-09-26 15:30:01.838: pcp_main pid 41329: LOG:  PCP process with pid: 90320 exit with SUCCESS.
2023-09-26 15:30:01.839: pcp_main pid 41329: LOG:  PCP process with pid: 90320 exits with status 0
2023-09-26 15:30:01.864: pcp_main pid 41329: LOG:  PCP process with pid: 90322 exit with SUCCESS.
2023-09-26 15:30:01.864: pcp_main pid 41329: LOG:  PCP process with pid: 90322 exits with status 0
2023-09-26 15:30:01.875: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90327 socket=7
2023-09-26 15:30:01.922: pcp_main pid 41329: LOG:  PCP process with pid: 90327 exit with SUCCESS.
2023-09-26 15:30:01.922: pcp_main pid 41329: LOG:  PCP process with pid: 90327 exits with status 0
2023-09-26 15:30:03.563: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:30:03.563: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:30:03.563: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:30:03.564: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:30:03.564: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:30:09.575: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:30:09.575: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:30:09.575: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:30:09.575: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:30:09.575: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:30:15.585: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:30:15.585: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:30:15.585: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:30:15.585: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:30:15.585: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:30:21.595: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:30:21.595: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:30:21.595: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:30:21.595: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:30:21.595: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:30:27.608: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:30:27.608: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:30:27.608: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:30:27.608: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:30:27.608: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:30:33.617: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:30:33.618: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:30:33.618: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:30:33.618: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:30:33.618: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:30:39.631: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:30:39.631: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:30:39.631: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:30:39.631: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:30:39.631: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:30:45.645: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:30:45.645: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:30:45.645: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:30:45.645: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:30:45.645: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:30:51.657: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:30:51.657: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:30:51.657: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:30:51.657: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:30:51.657: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:30:57.667: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:30:57.667: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:30:57.667: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:30:57.667: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:30:57.667: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:31:03.679: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:31:03.679: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:31:03.679: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:31:03.679: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:31:03.679: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:31:09.689: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:31:09.689: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:31:09.689: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:31:09.689: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:31:09.689: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:31:15.699: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:31:15.699: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:31:15.699: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:31:15.699: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:31:15.699: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:31:21.708: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:31:21.708: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:31:21.708: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:31:21.708: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:31:21.708: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:31:27.717: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:31:27.717: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:31:27.717: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:31:27.717: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:31:27.717: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:31:33.725: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:31:33.725: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:31:33.725: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:31:33.725: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:31:33.725: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:31:39.735: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:31:39.735: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:31:39.735: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:31:39.735: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:31:39.735: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:35:01.400: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90724 socket=7
2023-09-26 15:35:01.426: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90727 socket=7
2023-09-26 15:35:01.429: pcp_main pid 41329: LOG:  PCP process with pid: 90727 exit with SUCCESS.
2023-09-26 15:35:01.429: pcp_main pid 41329: LOG:  PCP process with pid: 90727 exits with status 0
2023-09-26 15:35:01.440: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90730 socket=7
2023-09-26 15:35:01.445: pcp_main pid 41329: LOG:  PCP process with pid: 90730 exit with SUCCESS.
2023-09-26 15:35:01.445: pcp_main pid 41329: LOG:  PCP process with pid: 90730 exits with status 0
2023-09-26 15:35:01.459: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90735 socket=7
2023-09-26 15:35:01.461: pcp_main pid 41329: LOG:  PCP process with pid: 90735 exit with SUCCESS.
2023-09-26 15:35:01.461: pcp_main pid 41329: LOG:  PCP process with pid: 90735 exits with status 0
2023-09-26 15:35:01.478: pcp_main pid 41329: LOG:  PCP process with pid: 90724 exit with SUCCESS.
2023-09-26 15:35:01.478: pcp_main pid 41329: LOG:  PCP process with pid: 90724 exits with status 0
2023-09-26 15:35:01.482: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90743 socket=7
2023-09-26 15:35:01.482: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90744 socket=7
2023-09-26 15:35:01.541: pcp_main pid 41329: LOG:  PCP process with pid: 90744 exit with SUCCESS.
2023-09-26 15:35:01.541: pcp_main pid 41329: LOG:  PCP process with pid: 90744 exits with status 0
2023-09-26 15:35:01.543: pcp_main pid 41329: LOG:  PCP process with pid: 90743 exit with SUCCESS.
2023-09-26 15:35:01.543: pcp_main pid 41329: LOG:  PCP process with pid: 90743 exits with status 0
2023-09-26 15:35:01.553: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90748 socket=7
2023-09-26 15:35:01.609: pcp_main pid 41329: LOG:  PCP process with pid: 90748 exit with SUCCESS.
2023-09-26 15:35:01.609: pcp_main pid 41329: LOG:  PCP process with pid: 90748 exits with status 0
2023-09-26 15:35:01.835: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90751 socket=7
2023-09-26 15:35:01.837: pcp_main pid 41329: LOG:  PCP process with pid: 90751 exit with SUCCESS.
2023-09-26 15:35:01.837: pcp_main pid 41329: LOG:  PCP process with pid: 90751 exits with status 0
2023-09-26 15:35:01.845: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90752 socket=7
2023-09-26 15:35:01.848: pcp_main pid 41329: LOG:  PCP process with pid: 90752 exit with SUCCESS.
2023-09-26 15:35:01.848: pcp_main pid 41329: LOG:  PCP process with pid: 90752 exits with status 0
2023-09-26 15:35:01.856: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90753 socket=7
2023-09-26 15:35:01.859: pcp_main pid 41329: LOG:  PCP process with pid: 90753 exit with SUCCESS.
2023-09-26 15:35:01.859: pcp_main pid 41329: LOG:  PCP process with pid: 90753 exits with status 0
2023-09-26 15:38:18.250: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90956 socket=7
2023-09-26 15:38:18.315: pcp_main pid 41329: LOG:  PCP process with pid: 90956 exit with SUCCESS.
2023-09-26 15:38:18.315: pcp_main pid 41329: LOG:  PCP process with pid: 90956 exits with status 0
2023-09-26 15:40:01.304: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91146 socket=7
2023-09-26 15:40:01.353: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91150 socket=7
2023-09-26 15:40:01.357: pcp_main pid 41329: LOG:  PCP process with pid: 91150 exit with SUCCESS.
2023-09-26 15:40:01.357: pcp_main pid 41329: LOG:  PCP process with pid: 91150 exits with status 0
2023-09-26 15:40:01.367: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91153 socket=7
2023-09-26 15:40:01.371: pcp_main pid 41329: LOG:  PCP process with pid: 91153 exit with SUCCESS.
2023-09-26 15:40:01.371: pcp_main pid 41329: LOG:  PCP process with pid: 91153 exits with status 0
2023-09-26 15:40:01.382: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91158 socket=7
2023-09-26 15:40:01.384: pcp_main pid 41329: LOG:  PCP process with pid: 91146 exit with SUCCESS.
2023-09-26 15:40:01.384: pcp_main pid 41329: LOG:  PCP process with pid: 91146 exits with status 0
2023-09-26 15:40:01.387: pcp_main pid 41329: LOG:  PCP process with pid: 91158 exit with SUCCESS.
2023-09-26 15:40:01.387: pcp_main pid 41329: LOG:  PCP process with pid: 91158 exits with status 0
2023-09-26 15:40:01.394: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91165 socket=7
2023-09-26 15:40:01.405: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91167 socket=7
2023-09-26 15:40:01.465: pcp_main pid 41329: LOG:  PCP process with pid: 91165 exit with SUCCESS.
2023-09-26 15:40:01.465: pcp_main pid 41329: LOG:  PCP process with pid: 91165 exits with status 0
2023-09-26 15:40:01.474: pcp_main pid 41329: LOG:  PCP process with pid: 91167 exit with SUCCESS.
2023-09-26 15:40:01.474: pcp_main pid 41329: LOG:  PCP process with pid: 91167 exits with status 0
2023-09-26 15:40:01.487: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91172 socket=7
2023-09-26 15:40:01.556: pcp_main pid 41329: LOG:  PCP process with pid: 91172 exit with SUCCESS.
2023-09-26 15:40:01.556: pcp_main pid 41329: LOG:  PCP process with pid: 91172 exits with status 0
2023-09-26 15:40:01.991: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91174 socket=7
2023-09-26 15:40:01.995: pcp_main pid 41329: LOG:  PCP process with pid: 91174 exit with SUCCESS.
2023-09-26 15:40:01.995: pcp_main pid 41329: LOG:  PCP process with pid: 91174 exits with status 0
2023-09-26 15:40:02.007: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91175 socket=7
2023-09-26 15:40:02.010: pcp_main pid 41329: LOG:  PCP process with pid: 91175 exit with SUCCESS.
2023-09-26 15:40:02.010: pcp_main pid 41329: LOG:  PCP process with pid: 91175 exits with status 0
2023-09-26 15:40:02.023: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91176 socket=7
2023-09-26 15:40:02.026: pcp_main pid 41329: LOG:  PCP process with pid: 91176 exit with SUCCESS.
2023-09-26 15:40:02.026: pcp_main pid 41329: LOG:  PCP process with pid: 91176 exits with status 0
2023-09-26 15:45:01.139: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91564 socket=7
2023-09-26 15:45:01.143: pcp_main pid 41329: LOG:  PCP process with pid: 91564 exit with SUCCESS.
2023-09-26 15:45:01.143: pcp_main pid 41329: LOG:  PCP process with pid: 91564 exits with status 0
2023-09-26 15:45:01.151: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91565 socket=7
2023-09-26 15:45:01.154: pcp_main pid 41329: LOG:  PCP process with pid: 91565 exit with SUCCESS.
2023-09-26 15:45:01.154: pcp_main pid 41329: LOG:  PCP process with pid: 91565 exits with status 0
2023-09-26 15:45:01.164: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91566 socket=7
2023-09-26 15:45:01.166: pcp_main pid 41329: LOG:  PCP process with pid: 91566 exit with SUCCESS.
2023-09-26 15:45:01.166: pcp_main pid 41329: LOG:  PCP process with pid: 91566 exits with status 0
2023-09-26 15:45:02.078: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91582 socket=7
2023-09-26 15:45:02.103: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91585 socket=7
2023-09-26 15:45:02.106: pcp_main pid 41329: LOG:  PCP process with pid: 91585 exit with SUCCESS.
2023-09-26 15:45:02.106: pcp_main pid 41329: LOG:  PCP process with pid: 91585 exits with status 0
2023-09-26 15:45:02.116: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91588 socket=7
2023-09-26 15:45:02.119: pcp_main pid 41329: LOG:  PCP process with pid: 91588 exit with SUCCESS.
2023-09-26 15:45:02.119: pcp_main pid 41329: LOG:  PCP process with pid: 91588 exits with status 0
2023-09-26 15:45:02.130: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91593 socket=7
2023-09-26 15:45:02.133: pcp_main pid 41329: LOG:  PCP process with pid: 91593 exit with SUCCESS.
2023-09-26 15:45:02.133: pcp_main pid 41329: LOG:  PCP process with pid: 91593 exits with status 0
2023-09-26 15:45:02.146: pcp_main pid 41329: LOG:  PCP process with pid: 91582 exit with SUCCESS.
2023-09-26 15:45:02.146: pcp_main pid 41329: LOG:  PCP process with pid: 91582 exits with status 0
2023-09-26 15:45:02.154: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91601 socket=7
2023-09-26 15:45:02.157: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91602 socket=7
2023-09-26 15:45:02.214: pcp_main pid 41329: LOG:  PCP process with pid: 91602 exit with SUCCESS.
2023-09-26 15:45:02.214: pcp_main pid 41329: LOG:  PCP process with pid: 91602 exits with status 0
2023-09-26 15:45:02.215: pcp_main pid 41329: LOG:  PCP process with pid: 91601 exit with SUCCESS.
2023-09-26 15:45:02.215: pcp_main pid 41329: LOG:  PCP process with pid: 91601 exits with status 0
2023-09-26 15:45:02.225: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91607 socket=7
2023-09-26 15:45:02.285: pcp_main pid 41329: LOG:  PCP process with pid: 91607 exit with SUCCESS.
2023-09-26 15:45:02.285: pcp_main pid 41329: LOG:  PCP process with pid: 91607 exits with status 0
2023-09-26 15:48:18.106: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91871 socket=7
2023-09-26 15:48:18.166: pcp_main pid 41329: LOG:  PCP process with pid: 91871 exit with SUCCESS.
2023-09-26 15:48:18.166: pcp_main pid 41329: LOG:  PCP process with pid: 91871 exits with status 0
2023-09-26 15:50:01.299: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92044 socket=7
2023-09-26 15:50:01.303: pcp_main pid 41329: LOG:  PCP process with pid: 92044 exit with SUCCESS.
2023-09-26 15:50:01.303: pcp_main pid 41329: LOG:  PCP process with pid: 92044 exits with status 0
2023-09-26 15:50:01.314: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92045 socket=7
2023-09-26 15:50:01.317: pcp_main pid 41329: LOG:  PCP process with pid: 92045 exit with SUCCESS.
2023-09-26 15:50:01.317: pcp_main pid 41329: LOG:  PCP process with pid: 92045 exits with status 0
2023-09-26 15:50:01.328: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92046 socket=7
2023-09-26 15:50:01.331: pcp_main pid 41329: LOG:  PCP process with pid: 92046 exit with SUCCESS.
2023-09-26 15:50:01.331: pcp_main pid 41329: LOG:  PCP process with pid: 92046 exits with status 0
2023-09-26 15:50:01.863: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92067 socket=7
2023-09-26 15:50:01.897: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92071 socket=7
2023-09-26 15:50:01.900: pcp_main pid 41329: LOG:  PCP process with pid: 92071 exit with SUCCESS.
2023-09-26 15:50:01.900: pcp_main pid 41329: LOG:  PCP process with pid: 92071 exits with status 0
2023-09-26 15:50:01.913: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92074 socket=7
2023-09-26 15:50:01.916: pcp_main pid 41329: LOG:  PCP process with pid: 92074 exit with SUCCESS.
2023-09-26 15:50:01.916: pcp_main pid 41329: LOG:  PCP process with pid: 92074 exits with status 0
2023-09-26 15:50:01.929: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92079 socket=7
2023-09-26 15:50:01.937: pcp_main pid 41329: LOG:  PCP process with pid: 92079 exit with SUCCESS.
2023-09-26 15:50:01.937: pcp_main pid 41329: LOG:  PCP process with pid: 92079 exits with status 0
2023-09-26 15:50:01.952: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92084 socket=7
2023-09-26 15:50:01.955: pcp_main pid 41329: LOG:  PCP process with pid: 92067 exit with SUCCESS.
2023-09-26 15:50:01.955: pcp_main pid 41329: LOG:  PCP process with pid: 92067 exits with status 0
2023-09-26 15:50:01.967: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92088 socket=7
2023-09-26 15:50:02.024: pcp_main pid 41329: LOG:  PCP process with pid: 92084 exit with SUCCESS.
2023-09-26 15:50:02.024: pcp_main pid 41329: LOG:  PCP process with pid: 92084 exits with status 0
2023-09-26 15:50:02.035: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92092 socket=7
2023-09-26 15:50:02.040: pcp_main pid 41329: LOG:  PCP process with pid: 92088 exit with SUCCESS.
2023-09-26 15:50:02.041: pcp_main pid 41329: LOG:  PCP process with pid: 92088 exits with status 0
2023-09-26 15:50:02.102: pcp_main pid 41329: LOG:  PCP process with pid: 92092 exit with SUCCESS.
2023-09-26 15:50:02.102: pcp_main pid 41329: LOG:  PCP process with pid: 92092 exits with status 0
2023-09-26 15:51:13.806: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92168 socket=7
2023-09-26 15:51:13.867: pcp_main pid 41329: LOG:  PCP process with pid: 92168 exit with SUCCESS.
2023-09-26 15:51:13.867: pcp_main pid 41329: LOG:  PCP process with pid: 92168 exits with status 0
2023-09-26 15:52:52.859: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92342 socket=7
2023-09-26 15:52:52.920: pcp_main pid 41329: LOG:  PCP process with pid: 92342 exit with SUCCESS.
2023-09-26 15:52:52.920: pcp_main pid 41329: LOG:  PCP process with pid: 92342 exits with status 0
2023-09-26 15:53:25.391: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92385 socket=7
2023-09-26 15:53:25.455: pcp_main pid 41329: LOG:  PCP process with pid: 92385 exit with SUCCESS.
2023-09-26 15:53:25.456: pcp_main pid 41329: LOG:  PCP process with pid: 92385 exits with status 0
2023-09-26 15:53:41.363: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92432 socket=7
2023-09-26 15:53:41.419: pcp_main pid 41329: LOG:  PCP process with pid: 92432 exit with SUCCESS.
2023-09-26 15:53:41.419: pcp_main pid 41329: LOG:  PCP process with pid: 92432 exits with status 0
2023-09-26 15:53:48.692: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92439 socket=7
2023-09-26 15:53:48.751: pcp_main pid 41329: LOG:  PCP process with pid: 92439 exit with SUCCESS.
2023-09-26 15:53:48.751: pcp_main pid 41329: LOG:  PCP process with pid: 92439 exits with status 0
2023-09-26 15:54:18.942: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92472 socket=7
2023-09-26 15:54:18.999: pcp_main pid 41329: LOG:  PCP process with pid: 92472 exit with SUCCESS.
2023-09-26 15:54:18.999: pcp_main pid 41329: LOG:  PCP process with pid: 92472 exits with status 0
2023-09-26 15:55:01.450: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92554 socket=7
2023-09-26 15:55:01.453: pcp_main pid 41329: LOG:  PCP process with pid: 92554 exit with SUCCESS.
2023-09-26 15:55:01.453: pcp_main pid 41329: LOG:  PCP process with pid: 92554 exits with status 0
2023-09-26 15:55:01.461: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92555 socket=7
2023-09-26 15:55:01.464: pcp_main pid 41329: LOG:  PCP process with pid: 92555 exit with SUCCESS.
2023-09-26 15:55:01.464: pcp_main pid 41329: LOG:  PCP process with pid: 92555 exits with status 0
2023-09-26 15:55:01.472: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92556 socket=7
2023-09-26 15:55:01.475: pcp_main pid 41329: LOG:  PCP process with pid: 92556 exit with SUCCESS.
2023-09-26 15:55:01.475: pcp_main pid 41329: LOG:  PCP process with pid: 92556 exits with status 0
2023-09-26 15:55:01.657: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92571 socket=7
2023-09-26 15:55:01.709: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92574 socket=7
2023-09-26 15:55:01.713: pcp_main pid 41329: LOG:  PCP process with pid: 92574 exit with SUCCESS.
2023-09-26 15:55:01.713: pcp_main pid 41329: LOG:  PCP process with pid: 92574 exits with status 0
2023-09-26 15:55:01.715: pcp_main pid 41329: LOG:  PCP process with pid: 92571 exit with SUCCESS.
2023-09-26 15:55:01.715: pcp_main pid 41329: LOG:  PCP process with pid: 92571 exits with status 0
2023-09-26 15:55:01.725: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92580 socket=7
2023-09-26 15:55:01.727: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92581 socket=7
2023-09-26 15:55:01.731: pcp_main pid 41329: LOG:  PCP process with pid: 92581 exit with SUCCESS.
2023-09-26 15:55:01.731: pcp_main pid 41329: LOG:  PCP process with pid: 92581 exits with status 0
2023-09-26 15:55:01.740: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92586 socket=7
2023-09-26 15:55:01.743: pcp_main pid 41329: LOG:  PCP process with pid: 92586 exit with SUCCESS.
2023-09-26 15:55:01.743: pcp_main pid 41329: LOG:  PCP process with pid: 92586 exits with status 0
2023-09-26 15:55:01.762: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92591 socket=7
2023-09-26 15:55:01.797: pcp_main pid 41329: LOG:  PCP process with pid: 92580 exit with SUCCESS.
2023-09-26 15:55:01.797: pcp_main pid 41329: LOG:  PCP process with pid: 92580 exits with status 0
2023-09-26 15:55:01.822: pcp_main pid 41329: LOG:  PCP process with pid: 92591 exit with SUCCESS.
2023-09-26 15:55:01.822: pcp_main pid 41329: LOG:  PCP process with pid: 92591 exits with status 0
2023-09-26 15:55:01.831: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92596 socket=7
2023-09-26 15:55:01.892: pcp_main pid 41329: LOG:  PCP process with pid: 92596 exit with SUCCESS.
2023-09-26 15:55:01.892: pcp_main pid 41329: LOG:  PCP process with pid: 92596 exits with status 0
2023-09-26 15:58:18.980: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92805 socket=7
2023-09-26 15:58:19.040: pcp_main pid 41329: LOG:  PCP process with pid: 92805 exit with SUCCESS.
2023-09-26 15:58:19.040: pcp_main pid 41329: LOG:  PCP process with pid: 92805 exits with status 0
2023-09-26 16:00:01.354: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92986 socket=7
2023-09-26 16:00:01.378: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92990 socket=7
2023-09-26 16:00:01.382: pcp_main pid 41329: LOG:  PCP process with pid: 92990 exit with SUCCESS.
2023-09-26 16:00:01.382: pcp_main pid 41329: LOG:  PCP process with pid: 92990 exits with status 0
2023-09-26 16:00:01.393: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92993 socket=7
2023-09-26 16:00:01.396: pcp_main pid 41329: LOG:  PCP process with pid: 92993 exit with SUCCESS.
2023-09-26 16:00:01.396: pcp_main pid 41329: LOG:  PCP process with pid: 92993 exits with status 0
2023-09-26 16:00:01.408: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92998 socket=7
2023-09-26 16:00:01.412: pcp_main pid 41329: LOG:  PCP process with pid: 92998 exit with SUCCESS.
2023-09-26 16:00:01.412: pcp_main pid 41329: LOG:  PCP process with pid: 92998 exits with status 0
2023-09-26 16:00:01.427: pcp_main pid 41329: LOG:  forked new pcp worker, pid=93003 socket=7
2023-09-26 16:00:01.432: pcp_main pid 41329: LOG:  PCP process with pid: 92986 exit with SUCCESS.
2023-09-26 16:00:01.432: pcp_main pid 41329: LOG:  PCP process with pid: 92986 exits with status 0
2023-09-26 16:00:01.442: pcp_main pid 41329: LOG:  forked new pcp worker, pid=93007 socket=7
2023-09-26 16:00:01.494: pcp_main pid 41329: LOG:  PCP process with pid: 93003 exit with SUCCESS.
2023-09-26 16:00:01.494: pcp_main pid 41329: LOG:  PCP process with pid: 93003 exits with status 0
2023-09-26 16:00:01.505: pcp_main pid 41329: LOG:  forked new pcp worker, pid=93011 socket=7
2023-09-26 16:00:01.513: pcp_main pid 41329: LOG:  PCP process with pid: 93007 exit with SUCCESS.
2023-09-26 16:00:01.513: pcp_main pid 41329: LOG:  PCP process with pid: 93007 exits with status 0
2023-09-26 16:00:01.574: pcp_main pid 41329: LOG:  PCP process with pid: 93011 exit with SUCCESS.
2023-09-26 16:00:01.574: pcp_main pid 41329: LOG:  PCP process with pid: 93011 exits with status 0
2023-09-26 16:00:01.615: pcp_main pid 41329: LOG:  forked new pcp worker, pid=93014 socket=7
2023-09-26 16:00:01.619: pcp_main pid 41329: LOG:  PCP process with pid: 93014 exit with SUCCESS.
2023-09-26 16:00:01.619: pcp_main pid 41329: LOG:  PCP process with pid: 93014 exits with status 0
2023-09-26 16:00:01.629: pcp_main pid 41329: LOG:  forked new pcp worker, pid=93015 socket=7
2023-09-26 16:00:01.631: pcp_main pid 41329: LOG:  PCP process with pid: 93015 exit with SUCCESS.
2023-09-26 16:00:01.631: pcp_main pid 41329: LOG:  PCP process with pid: 93015 exits with status 0
2023-09-26 16:00:01.641: pcp_main pid 41329: LOG:  forked new pcp worker, pid=93016 socket=7
2023-09-26 16:00:01.644: pcp_main pid 41329: LOG:  PCP process with pid: 93016 exit with SUCCESS.
2023-09-26 16:00:01.644: pcp_main pid 41329: LOG:  PCP process with pid: 93016 exits with status 0
2023-09-26 16:00:23.530: pcp_main pid 41329: LOG:  forked new pcp worker, pid=93039 socket=7
2023-09-26 16:00:23.534: pcp_main pid 41329: LOG:  PCP process with pid: 93039 exit with SUCCESS.
2023-09-26 16:00:23.534: pcp_main pid 41329: LOG:  PCP process with pid: 93039 exits with status 0
pgpool-TueNEW.log (79,420 bytes)   

pengbo

2023-10-03 14:42

developer   ~0004434

Could you share pgpool.conf?

philB

2023-10-03 16:33

reporter   ~0004436

pgpool.conf (54,353 bytes)    
# ----------------------------
# pgPool-II configuration file
# ----------------------------
#
# This file consists of lines of the form:
#
#   name = value
#
# Whitespace may be used.  Comments are introduced with "#" anywhere on a line.
# The complete list of parameter names and allowed values can be found in the
# pgPool-II documentation.
#
# This file is read on server startup and when the server receives a SIGHUP
# signal.  If you edit the file on a running system, you have to SIGHUP the
# server for the changes to take effect, or use "pgpool reload".  Some
# parameters, which are marked below, require a server shutdown and restart to
# take effect.
#

#------------------------------------------------------------------------------
# BACKEND CLUSTERING MODE
# Choose one of: 'streaming_replication', 'native_replication',
#	'logical_replication', 'slony', 'raw' or 'snapshot_isolation'
# (change requires restart)
#------------------------------------------------------------------------------

backend_clustering_mode = 'streaming_replication'

#------------------------------------------------------------------------------
# CONNECTIONS
#------------------------------------------------------------------------------

# - pgpool Connection Settings -

#listen_addresses = 'localhost'
listen_addresses = '*'
                                   # what host name(s) or IP address(es) to listen on;
                                   # comma-separated list of addresses;
                                   # defaults to 'localhost'; use '*' for all
                                   # (change requires restart)
#port = 9999
port = 5432
                                   # Port number
                                   # (change requires restart)
#unix_socket_directories = '/var/run/postgresql'
unix_socket_directories = '/var/run/pgpool'
                                   # Unix domain socket path(s)
                                   # The Debian package defaults to
                                   # /var/run/postgresql
                                   # (change requires restart)
#unix_socket_group = ''
                                   # The Owner group of Unix domain socket(s)
                                   # (change requires restart)
#unix_socket_permissions = 0777
                                   # Permissions of Unix domain socket(s)
                                   # (change requires restart)
#reserved_connections = 0
reserved_connections = 10
                                   # Number of reserved connections.
                                   # Pgpool-II does not accept connections if over
                                   # num_init_chidlren - reserved_connections.


# - pgpool Communication Manager Connection Settings -

#pcp_listen_addresses = 'localhost'
pcp_listen_addresses = '*'
                                   # what host name(s) or IP address(es) to listen on;
                                   # comma-separated list of addresses;
                                   # defaults to 'localhost'; use '*' for all
                                   # (change requires restart)
#pcp_port = 9898
                                   # Port number for pcp
                                   # (change requires restart)
#pcp_socket_dir = '/var/run/postgresql'
pcp_socket_dir = '/var/run/pgpool'
                                   # Unix domain socket path for pcp
                                   # The Debian package defaults to
                                   # /var/run/postgresql
                                   # (change requires restart)
#listen_backlog_multiplier = 2
                                   # Set the backlog parameter of listen(2) to
                                   # num_init_children * listen_backlog_multiplier.
                                   # (change requires restart)
#serialize_accept = off
                                   # whether to serialize accept() call to avoid thundering herd problem
                                   # (change requires restart)

# - Backend Connection Settings -

#backend_hostname0 = 'host1'
backend_hostname0 = 'servdbmopp001'
                                   # Host name or IP address to connect to for backend 0
backend_port0 = 5432
                                   # Port number for backend 0
backend_weight0 = 1
                                   # Weight for backend 0 (only in load balancing mode)
backend_data_directory0 = '/data/pgsql/15/data'
                                   # Data directory for backend 0
#backend_flag0 = 'ALLOW_TO_FAILOVER'
backend_flag0 = 'ALLOW_TO_FAILOVER'
                                   # Controls various backend behavior
                                   # ALLOW_TO_FAILOVER, DISALLOW_TO_FAILOVER
                                   # or ALWAYS_PRIMARY
#backend_application_name0 = 'server0'
backend_application_name0 = 'patroni1'
                                   # walsender's application_name, used for "show pool_nodes" command
#backend_hostname1 = 'host2'
backend_hostname1 = 'servdbmopp011'
#backend_port1 = 5433
backend_port1 = 5432
backend_weight1 = 1
backend_data_directory1 = '/data/pgsql/15/data'
backend_flag1 = 'ALLOW_TO_FAILOVER'
#backend_application_name1 = 'server1'
backend_application_name1 = 'patroni2'

backend_hostname2 = 'servdbmopp021'
backend_port2 = 5432
backend_weight2 = 1
backend_data_directory2 = '/data/pgsql/15/data'
backend_flag2 = 'ALLOW_TO_FAILOVER'
backend_application_name2 = 'patroni3'

# - Authentication -

#enable_pool_hba = off
enable_pool_hba = on
                                   # Use pool_hba.conf for client authentication
#pool_passwd = 'pool_passwd'
                                   # File name of pool_passwd for md5 authentication.
                                   # "" disables pool_passwd.
                                   # (change requires restart)
#authentication_timeout = 1min
                                   # Delay in seconds to complete client authentication
                                   # 0 means no timeout.

#allow_clear_text_frontend_auth = off
                                   # Allow Pgpool-II to use clear text password authentication
                                   # with clients, when pool_passwd does not
                                   # contain the user password

# - SSL Connections -

#ssl = off
                                   # Enable SSL support
                                   # (change requires restart)
#ssl_key = 'server.key'
                                   # SSL private key file
                                   # (change requires restart)
#ssl_cert = 'server.crt'
                                   # SSL public certificate file
                                   # (change requires restart)
#ssl_ca_cert = ''
                                   # Single PEM format file containing
                                   # CA root certificate(s)
                                   # (change requires restart)
#ssl_ca_cert_dir = ''
                                   # Directory containing CA root certificate(s)
                                   # (change requires restart)
#ssl_crl_file = ''
                                   # SSL certificate revocation list file
                                   # (change requires restart)

#ssl_ciphers = 'HIGH:MEDIUM:+3DES:!aNULL'
                                   # Allowed SSL ciphers
                                   # (change requires restart)
#ssl_prefer_server_ciphers = off
                                   # Use server's SSL cipher preferences,
                                   # rather than the client's
                                   # (change requires restart)
#ssl_ecdh_curve = 'prime256v1'
                                   # Name of the curve to use in ECDH key exchange
#ssl_dh_params_file = ''
                                   # Name of the file containing Diffie-Hellman parameters used
                                   # for so-called ephemeral DH family of SSL cipher.
#ssl_passphrase_command=''
                                   # Sets an external command to be invoked when a passphrase
                                   # for decrypting an SSL file needs to be obtained
                                   # (change requires restart)

#------------------------------------------------------------------------------
# POOLS
#------------------------------------------------------------------------------

# - Concurrent session and pool size -

#process_management_mode = static
                                   # process management mode for child processes
                                   # Valid options:
                                   # static: all children are pre-forked at startup
                                   # dynamic: child processes are spawned on demand.
                                   #      number of idle child processes at any time are
                                   #      configured by min_spare_children and max_spare_children

#process_management_strategy = gentle
                                   # process management strategy to satisfy spare processes
                                   # Valid options:
                                   #
                                   #    lazy: In this mode, the scale-down is performed gradually
                                   #     and only gets triggered when excessive spare processes count
                                   #     remains high for more than 5 mins
                                   #
                                   #    gentle: In this mode, the scale-down is performed gradually
                                   #     and only gets triggered when excessive spare processes count
                                   #     remains high for more than 2 mins
                                   #
                                   #    aggressive: In this mode, the scale-down is performed aggressively
                                   #     and gets triggered more frequently in case of higher spare processes.
                                   #     This mode uses faster and slightly less smart process selection criteria
                                   #     to identify the child processes that can be serviced to satisfy
                                   #     max_spare_children
                                   #
                                   # (Only applicable for dynamic process management mode)

#num_init_children = 32
num_init_children = 400
                                   # Maximum Number of concurrent sessions allowed
                                   # (change requires restart)
#min_spare_children = 5
                                   # Minimum number of spare child processes waiting for connection
                                   # (Only applicable for dynamic process management mode)

#max_spare_children = 10
                                   # Maximum number of idle child processes waiting for connection
                                   # (Only applicable for dynamic process management mode)

#max_pool = 4
max_pool = 5
                                   # Number of connection pool caches per connection
                                   # (change requires restart)

# - Life time -

#child_life_time = 5min
                                   # Pool exits after being idle for this many seconds
#child_max_connections = 0
                                   # Pool exits after receiving that many connections
                                   # 0 means no exit
#connection_life_time = 0
                                   # Connection to backend closes after being idle for this many seconds
                                   # 0 means no close
#client_idle_limit = 0
                                   # Client is disconnected after being idle for that many seconds
                                   # (even inside an explicit transactions!)
                                   # 0 means no disconnection


#------------------------------------------------------------------------------
# LOGS
#------------------------------------------------------------------------------

# - Where to log -

log_destination = 'stderr'
                                   # Where to log
                                   # Valid values are combinations of stderr,
                                   # and syslog. Default to stderr.

# - What to log -

#log_line_prefix = '%m: %a pid %p: '   # printf-style string to output at beginning of each log line.

#log_connections = off
                                   # Log connections
#log_disconnections = off
                                   # Log disconnections
#log_hostname = off
                                   # Hostname will be shown in ps status
                                   # and in logs if connections are logged
#log_statement = off
                                   # Log all statements
#log_per_node_statement = off
                                   # Log all statements
                                   # with node and backend informations
#log_client_messages = off
                                   # Log any client messages
#log_standby_delay = 'if_over_threshold'
                                   # Log standby delay
                                   # Valid values are combinations of always,
                                   # if_over_threshold, none

# - Syslog specific -

#syslog_facility = 'LOCAL0'
                                   # Syslog local facility. Default to LOCAL0
#syslog_ident = 'pgpool'
                                   # Syslog program identification string
                                   # Default to 'pgpool'

# - Debug -

#log_error_verbosity = default          # terse, default, or verbose messages

#client_min_messages = notice           # values in order of decreasing detail:
                                        #   debug5
                                        #   debug4
                                        #   debug3
                                        #   debug2
                                        #   debug1
                                        #   log
                                        #   notice
                                        #   warning
                                        #   error

#log_min_messages = warning             # values in order of decreasing detail:
                                        #   debug5
                                        #   debug4
                                        #   debug3
                                        #   debug2
                                        #   debug1
                                        #   info
                                        #   notice
                                        #   warning
                                        #   error
                                        #   log
                                        #   fatal
                                        #   panic

# This is used when logging to stderr:
logging_collector = on
                                        # Enable capturing of stderr
                                        # into log files.
                                        # (change requires restart)

# -- Only used if logging_collector is on ---

log_directory = '/var/log/pgpool_log'
                                        # directory where log files are written,
                                        # can be absolute
log_filename = 'pgpool-%a.log'
                                        # log file name pattern,
                                        # can include strftime() escapes

#log_file_mode = 0600
log_file_mode = 0644
                                        # creation mode for log files,
                                        # begin with 0 to use octal notation

log_truncate_on_rotation = on
                                        # If on, an existing log file with the
                                        # same name as the new log file will be
                                        # truncated rather than appended to.
                                        # But such truncation only occurs on
                                        # time-driven rotation, not on restarts
                                        # or size-driven rotation.  Default is
                                        # off, meaning append to existing files
                                        # in all cases.

log_rotation_age = 1d
                                        # Automatic rotation of logfiles will
                                        # happen after that (minutes)time.
                                        # 0 disables time based rotation.
log_rotation_size = 0 
                                        # Automatic rotation of logfiles will
                                        # happen after that much (KB) log output.
                                        # 0 disables size based rotation.
#------------------------------------------------------------------------------
# FILE LOCATIONS
#------------------------------------------------------------------------------

#pid_file_name = '/var/run/pgpool/pgpool.pid'
                                   # PID file name
                                   # Can be specified as relative to the"
                                   # location of pgpool.conf file or
                                   # as an absolute path
                                   # (change requires restart)
#logdir = '/tmp'
                                   # Directory of pgPool status file
                                   # (change requires restart)


#------------------------------------------------------------------------------
# CONNECTION POOLING
#------------------------------------------------------------------------------

#connection_cache = on
                                   # Activate connection pools
                                   # (change requires restart)

                                   # Semicolon separated list of queries
                                   # to be issued at the end of a session
                                   # The default is for 8.3 and later
#reset_query_list = 'ABORT; DISCARD ALL'
                                   # The following one is for 8.2 and before
#reset_query_list = 'ABORT; RESET ALL; SET SESSION AUTHORIZATION DEFAULT'


#------------------------------------------------------------------------------
# REPLICATION MODE
#------------------------------------------------------------------------------

#replicate_select = off
                                   # Replicate SELECT statements
                                   # when in replication mode
                                   # replicate_select is higher priority than
                                   # load_balance_mode.

#insert_lock = off
                                   # Automatically locks a dummy row or a table
                                   # with INSERT statements to keep SERIAL data
                                   # consistency
                                   # Without SERIAL, no lock will be issued
#lobj_lock_table = ''
                                   # When rewriting lo_creat command in
                                   # replication mode, specify table name to
                                   # lock

# - Degenerate handling -

#replication_stop_on_mismatch = off
                                   # On disagreement with the packet kind
                                   # sent from backend, degenerate the node
                                   # which is most likely "minority"
                                   # If off, just force to exit this session

#failover_if_affected_tuples_mismatch = off
                                   # On disagreement with the number of affected
                                   # tuples in UPDATE/DELETE queries, then
                                   # degenerate the node which is most likely
                                   # "minority".
                                   # If off, just abort the transaction to
                                   # keep the consistency


#------------------------------------------------------------------------------
# LOAD BALANCING MODE
#------------------------------------------------------------------------------

#load_balance_mode = on
load_balance_mode = off
                                   # Activate load balancing mode
                                   # (change requires restart)
#ignore_leading_white_space = on
                                   # Ignore leading white spaces of each query
#read_only_function_list = ''
                                   # Comma separated list of function names
                                   # that don't write to database
                                   # Regexp are accepted
#write_function_list = ''
                                   # Comma separated list of function names
                                   # that write to database
                                   # Regexp are accepted
                                   # If both read_only_function_list and write_function_list
                                   # is empty, function's volatile property is checked.
                                   # If it's volatile, the function is regarded as a
                                   # writing function.

#primary_routing_query_pattern_list = ''
                                   # Semicolon separated list of query patterns
                                   # that should be sent to primary node
                                   # Regexp are accepted
                                   # valid for streaming replicaton mode only.

#database_redirect_preference_list = ''
                                   # comma separated list of pairs of database and node id.
                                   # example: postgres:primary,mydb[0-4]:1,mydb[5-9]:2'
                                   # valid for streaming replicaton mode only.

#app_name_redirect_preference_list = ''
                                   # comma separated list of pairs of app name and node id.
                                   # example: 'psql:primary,myapp[0-4]:1,myapp[5-9]:standby'
                                   # valid for streaming replicaton mode only.
#allow_sql_comments = off
                                   # if on, ignore SQL comments when judging if load balance or
                                   # query cache is possible.
                                   # If off, SQL comments effectively prevent the judgment
                                   # (pre 3.4 behavior).

#disable_load_balance_on_write = 'transaction'
                                   # Load balance behavior when write query is issued
                                   # in an explicit transaction.
                                   #
                                   # Valid values:
                                   #
                                   # 'transaction' (default):
                                   #     if a write query is issued, subsequent
                                   #     read queries will not be load balanced
                                   #     until the transaction ends.
                                   #
                                   # 'trans_transaction':
                                   #     if a write query is issued, subsequent
                                   #     read queries in an explicit transaction
                                   #     will not be load balanced until the session ends.
                                   #
                                   # 'dml_adaptive':
                                   #     Queries on the tables that have already been
                                   #     modified within the current explicit transaction will
                                   #     not be load balanced until the end of the transaction.
                                   #
                                   # 'always':
                                   #     if a write query is issued, read queries will
                                   #     not be load balanced until the session ends.
                                   #
                                   # Note that any query not in an explicit transaction
                                   # is not affected by the parameter except 'always'.

#dml_adaptive_object_relationship_list= ''
                                   # comma separated list of object pairs
                                   # [object]:[dependent-object], to disable load balancing
                                   # of dependent objects within the explicit transaction
                                   # after WRITE statement is issued on (depending-on) object.
                                   #
                                   # example: 'tb_t1:tb_t2,insert_tb_f_func():tb_f,tb_v:my_view'
                                   # Note: function name in this list must also be present in
                                   # the write_function_list
                                   # only valid for disable_load_balance_on_write = 'dml_adaptive'.

#statement_level_load_balance = off
                                   # Enables statement level load balancing

#------------------------------------------------------------------------------
# STREAMING REPLICATION MODE
#------------------------------------------------------------------------------

# - Streaming -

sr_check_period = 10
                                   # Streaming replication check period
                                   # Disabled (0) by default
#sr_check_user = 'nobody'
sr_check_user = 'postgres'
                                   # Streaming replication check user
                                   # This is neccessary even if you disable streaming
                                   # replication delay check by sr_check_period = 0
#sr_check_password = ''
                                   # Password for streaming replication check user
                                   # Leaving it empty will make Pgpool-II to first look for the
                                   # Password in pool_passwd file before using the empty password

sr_check_database = 'postgres'
                                   # Database name for streaming replication check
#delay_threshold = 0
                                   # Threshold before not dispatching query to standby node
                                   # Unit is in bytes
                                   # Disabled (0) by default
#delay_threshold_by_time = 0
delay_threshold_by_time = 60
                                   # Threshold before not dispatching query to standby node
                                   # Unit is in second(s)
                                   # Disabled (0) by default

#prefer_lower_delay_standby = off
                                   # If delay_threshold is set larger than 0, Pgpool-II send to
                                   # the primary when selected node is delayed over delay_threshold.
                                   # If this is set to on, Pgpool-II send query to other standby
                                   # delayed lower.

# - Special commands -

#follow_primary_command = ''
                                   # Executes this command after main node failover
                                   # Special values:
                                   #   %d = failed node id
                                   #   %h = failed node host name
                                   #   %p = failed node port number
                                   #   %D = failed node database cluster path
                                   #   %m = new main node id
                                   #   %H = new main node hostname
                                   #   %M = old main node id
                                   #   %P = old primary node id
                                   #   %r = new main port number
                                   #   %R = new main database cluster path
                                   #   %N = old primary node hostname
                                   #   %S = old primary node port number
                                   #   %% = '%' character

#------------------------------------------------------------------------------
# HEALTH CHECK GLOBAL PARAMETERS
#------------------------------------------------------------------------------

#health_check_period = 0
health_check_period = 5
                                   # Health check period
                                   # Disabled (0) by default
#health_check_timeout = 20
                                   # Health check timeout
                                   # 0 means no timeout
#health_check_user = 'nobody'
health_check_user = 'postgres'
                                   # Health check user
#health_check_password = ''
                                   # Password for health check user
                                   # Leaving it empty will make Pgpool-II to first look for the
                                   # Password in pool_passwd file before using the empty password

#health_check_database = ''
health_check_database = 'postgres'
                                   # Database name for health check. If '', tries 'postgres' frist, 
#health_check_max_retries = 0
health_check_max_retries = 1
                                   # Maximum number of times to retry a failed health check before giving up.
#health_check_retry_delay = 1
                                   # Amount of time to wait (in seconds) between retries.
#connect_timeout = 10000
                                   # Timeout value in milliseconds before giving up to connect to backend.
                                   # Default is 10000 ms (10 second). Flaky network user may want to increase
                                   # the value. 0 means no timeout.
                                   # Note that this value is not only used for health check,
                                   # but also for ordinary conection to backend.

#------------------------------------------------------------------------------
# HEALTH CHECK PER NODE PARAMETERS (OPTIONAL)
#------------------------------------------------------------------------------
#health_check_period0 = 0
#health_check_timeout0 = 20
#health_check_user0 = 'nobody'
#health_check_password0 = ''
#health_check_database0 = ''
#health_check_max_retries0 = 0
#health_check_retry_delay0 = 1
#connect_timeout0 = 10000

#------------------------------------------------------------------------------
# FAILOVER AND FAILBACK
#------------------------------------------------------------------------------

#failover_command = ''
                                   # Executes this command at failover
                                   # Special values:
                                   #   %d = failed node id
                                   #   %h = failed node host name
                                   #   %p = failed node port number
                                   #   %D = failed node database cluster path
                                   #   %m = new main node id
                                   #   %H = new main node hostname
                                   #   %M = old main node id
                                   #   %P = old primary node id
                                   #   %r = new main port number
                                   #   %R = new main database cluster path
                                   #   %N = old primary node hostname
                                   #   %S = old primary node port number
                                   #   %% = '%' character
#failback_command = ''
                                   # Executes this command at failback.
                                   # Special values:
                                   #   %d = failed node id
                                   #   %h = failed node host name
                                   #   %p = failed node port number
                                   #   %D = failed node database cluster path
                                   #   %m = new main node id
                                   #   %H = new main node hostname
                                   #   %M = old main node id
                                   #   %P = old primary node id
                                   #   %r = new main port number
                                   #   %R = new main database cluster path
                                   #   %N = old primary node hostname
                                   #   %S = old primary node port number
                                   #   %% = '%' character

failover_on_backend_error = on
#failover_on_backend_error = off
                                   # Initiates failover when reading/writing to the
                                   # backend communication socket fails
                                   # If set to off, pgpool will report an
                                   # error and disconnect the session.

failover_on_backend_shutdown = off
#failover_on_backend_shutdown = on
                                   # Initiates failover when backend is shutdown,
				   # or backend process is killed.
                                   # If set to off, pgpool will report an
                                   # error and disconnect the session.

#detach_false_primary = off
                                   # Detach false primary if on. Only
                                   # valid in streaming replicaton
                                   # mode and with PostgreSQL 9.6 or
                                   # after.

#search_primary_node_timeout = 5min
search_primary_node_timeout = 1min
                                   # Timeout in seconds to search for the
                                   # primary node when a failover occurs.
                                   # 0 means no timeout, keep searching
                                   # for a primary node forever.

#------------------------------------------------------------------------------
# ONLINE RECOVERY
#------------------------------------------------------------------------------

#recovery_user = 'nobody'
                                   # Online recovery user
#recovery_password = ''
                                   # Online recovery password
                                   # Leaving it empty will make Pgpool-II to first look for the
                                   # Password in pool_passwd file before using the empty password

#recovery_1st_stage_command = ''
                                   # Executes a command in first stage
#recovery_2nd_stage_command = ''
                                   # Executes a command in second stage
#recovery_timeout = 90
                                   # Timeout in seconds to wait for the
                                   # recovering node's postmaster to start up
                                   # 0 means no wait
#client_idle_limit_in_recovery = 0
                                   # Client is disconnected after being idle
                                   # for that many seconds in the second stage
                                   # of online recovery
                                   # 0 means no disconnection
                                   # -1 means immediate disconnection

#auto_failback = off
auto_failback = on
                                   # Dettached backend node reattach automatically
                                   # if replication_state is 'streaming'.
#auto_failback_interval = 1min
auto_failback_interval = 0
                                   # Min interval of executing auto_failback in
                                   # seconds.

#------------------------------------------------------------------------------
# WATCHDOG
#------------------------------------------------------------------------------

# - Enabling -

#use_watchdog = off
use_watchdog = on
                                    # Activates watchdog
                                    # (change requires restart)

# -Connection to up stream servers -

#trusted_servers = ''
                                    # trusted server list which are used
                                    # to confirm network connection
                                    # (hostA,hostB,hostC,...)
                                    # (change requires restart)

#trusted_server_command = 'ping -q -c3 %h'
                                    # Command to excute when communicate trusted server.
                                    # Special values:
                                    #   %h = host name specified by trusted_servers

# - Watchdog communication Settings -

hostname0 = 'servasmogp001'
                                    # Host name or IP address of pgpool node
                                    # for watchdog connection
                                    # (change requires restart)
wd_port0 = 9000
                                    # Port number for watchdog service
                                    # (change requires restart)
#pgpool_port0 = 9999
pgpool_port0 = 5432
                                    # Port number for pgpool
                                    # (change requires restart)

#hostname1 = ''
hostname1 = 'servasmogp002'
wd_port1 = 9000
#pgpool_port1 = 9999
pgpool_port1 = 5432

#hostname2 = ''
#wd_port2 = 9000
#pgpool_port2 = 9999

#wd_priority = 1
                                    # priority of this watchdog in leader election
                                    # (change requires restart)

#wd_authkey = ''
                                    # Authentication key for watchdog communication
                                    # (change requires restart)

#wd_ipc_socket_dir = '/var/run/postgresql'
wd_ipc_socket_dir = '/var/run/pgpool'
                                    # Unix domain socket path for watchdog IPC socket
                                    # The Debian package defaults to
                                    # /var/run/postgresql
                                    # (change requires restart)


# - Virtual IP control Setting -

#delegate_ip = ''
delegate_ip = '192.168.105.243'		# servasmogp-vip
                                    # delegate IP address
                                    # If this is empty, virtual IP never bring up.
                                    # (change requires restart)
#if_cmd_path = '/sbin'
                                    # path to the directory where if_up/down_cmd exists
                                    # If if_up/down_cmd starts with "/", if_cmd_path will be ignored.
                                    # (change requires restart)
#if_up_cmd = '/usr/bin/sudo /sbin/ip addr add $_IP_$/24 dev eth0 label eth0:0'
if_up_cmd = '/usr/bin/sudo /sbin/ip addr add $_IP_$/24 dev ens192 label ens192:0'
                                    # startup delegate IP command
                                    # (change requires restart)
#if_down_cmd = '/usr/bin/sudo /sbin/ip addr del $_IP_$/24 dev eth0'
if_down_cmd = '/usr/bin/sudo /sbin/ip addr del $_IP_$/24 dev ens192'
                                    # shutdown delegate IP command
                                    # (change requires restart)
#arping_path = '/usr/sbin'
                                    # arping command path
                                    # If arping_cmd starts with "/", if_cmd_path will be ignored.
                                    # (change requires restart)
#arping_cmd = '/usr/bin/sudo /usr/sbin/arping -U $_IP_$ -w 1 -I eth0'
arping_cmd = '/usr/bin/sudo /usr/sbin/arping -U $_IP_$ -w 1 -I ens192'
                                    # arping command
                                    # (change requires restart)

#ping_path = '/bin'
                                    # ping command path
                                    # (change requires restart)

# - Behaivor on escalation Setting -

#clear_memqcache_on_escalation = on
                                    # Clear all the query cache on shared memory
                                    # when standby pgpool escalate to active pgpool
                                    # (= virtual IP holder).
                                    # This should be off if client connects to pgpool
                                    # not using virtual IP.
                                    # (change requires restart)
#wd_escalation_command = ''
                                    # Executes this command at escalation on new active pgpool.
                                    # (change requires restart)
#wd_de_escalation_command = ''
                                    # Executes this command when leader pgpool resigns from being leader.
                                    # (change requires restart)

# - Watchdog consensus settings for failover -

#failover_when_quorum_exists = on
                                    # Only perform backend node failover
                                    # when the watchdog cluster holds the quorum
                                    # (change requires restart)

#failover_require_consensus = on
                                    # Perform failover when majority of Pgpool-II nodes
                                    # aggrees on the backend node status change
                                    # (change requires restart)

#allow_multiple_failover_requests_from_node = off
                                    # A Pgpool-II node can cast multiple votes
                                    # for building the consensus on failover
                                    # (change requires restart)


#enable_consensus_with_half_votes = off
enable_consensus_with_half_votes = on
                                    # apply majority rule for consensus and quorum computation
                                    # at 50% of votes in a cluster with even number of nodes.
                                    # when enabled the existence of quorum and consensus
                                    # on failover is resolved after receiving half of the
                                    # total votes in the cluster, otherwise both these
                                    # decisions require at least one more vote than
                                    # half of the total votes.
                                    # (change requires restart)

# - Watchdog cluster membership settings for quorum computation -

#wd_remove_shutdown_nodes = off
                                    # when enabled cluster membership of properly shutdown
                                    # watchdog nodes gets revoked, After that the node does
                                    # not count towards the quorum and consensus computations

#wd_lost_node_removal_timeout = 0s
                                    # Timeout after which the cluster membership of LOST watchdog
                                    # nodes gets revoked. After that the node node does not
                                    # count towards the quorum and consensus computations
                                    # setting timeout to 0 will never revoke the membership
                                    # of LOST nodes

#wd_no_show_node_removal_timeout = 0s
                                    # Time to wait for Watchdog node to connect to the cluster.
                                    # After that time the cluster membership of NO-SHOW node gets
                                    # revoked and it does not count towards the quorum and
                                    # consensus computations
                                    # setting timeout to 0 will not revoke the membership
                                    # of NO-SHOW nodes


# - Lifecheck Setting -

# -- common --

#wd_monitoring_interfaces_list = ''
wd_monitoring_interfaces_list = 'ens192'
                                    # Comma separated list of interfaces names to monitor.
                                    # if any interface from the list is active the watchdog will
                                    # consider the network is fine
                                    # 'any' to enable monitoring on all interfaces except loopback
                                    # '' to disable monitoring
                                    # (change requires restart)

#wd_lifecheck_method = 'heartbeat'
wd_lifecheck_method = 'heartbeat'
                                    # Method of watchdog lifecheck ('heartbeat' or 'query' or 'external')
                                    # (change requires restart)
#wd_interval = 10
                                    # lifecheck interval (sec) > 0
                                    # (change requires restart)

# -- heartbeat mode --

#heartbeat_hostname0 = ''
heartbeat_hostname0 = 'servasmogp001'
                                    # Host name or IP address used
                                    # for sending heartbeat signal.
                                    # (change requires restart)
heartbeat_port0 = 9694
                                    # Port number used for receiving/sending heartbeat signal
                                    # Usually this is the same as heartbeat_portX.
                                    # (change requires restart)
#heartbeat_device0 = ''
heartbeat_device0 = 'ens192'
                                    # Name of NIC device (such like 'eth0')
                                    # used for sending/receiving heartbeat
                                    # signal to/from destination 0.
                                    # This works only when this is not empty
                                    # and pgpool has root privilege.
                                    # (change requires restart)

heartbeat_hostname1 = 'servasmogp002'
heartbeat_port1 = 9694
heartbeat_device1 = 'ens192'
#heartbeat_hostname2 = ''
#heartbeat_port2 = 9694
#heartbeat_device2 = ''

#wd_heartbeat_keepalive = 2
                                    # Interval time of sending heartbeat signal (sec)
                                    # (change requires restart)
#wd_heartbeat_deadtime = 30
                                    # Deadtime interval for heartbeat signal (sec)
                                    # (change requires restart)

# -- query mode --

#wd_life_point = 3
                                    # lifecheck retry times
                                    # (change requires restart)
#wd_lifecheck_query = 'SELECT 1'
                                    # lifecheck query to pgpool from watchdog
                                    # (change requires restart)
#wd_lifecheck_dbname = 'template1'
                                    # Database name connected for lifecheck
                                    # (change requires restart)
#wd_lifecheck_user = 'nobody'
                                    # watchdog user monitoring pgpools in lifecheck
                                    # (change requires restart)
#wd_lifecheck_password = ''
                                    # Password for watchdog user in lifecheck
                                    # Leaving it empty will make Pgpool-II to first look for the
                                    # Password in pool_passwd file before using the empty password
                                    # (change requires restart)

#------------------------------------------------------------------------------
# OTHERS
#------------------------------------------------------------------------------
#relcache_expire = 0
                                   # Life time of relation cache in seconds.
                                   # 0 means no cache expiration(the default).
                                   # The relation cache is used for cache the
                                   # query result against PostgreSQL system
                                   # catalog to obtain various information
                                   # including table structures or if it's a
                                   # temporary table or not. The cache is
                                   # maintained in a pgpool child local memory
                                   # and being kept as long as it survives.
                                   # If someone modify the table by using
                                   # ALTER TABLE or some such, the relcache is
                                   # not consistent anymore.
                                   # For this purpose, cache_expiration
                                   # controls the life time of the cache.
#relcache_size = 256
                                   # Number of relation cache
                                   # entry. If you see frequently:
                                   # "pool_search_relcache: cache replacement happend"
                                   # in the pgpool log, you might want to increate this number.

#check_temp_table = catalog
                                   # Temporary table check method. catalog, trace or none.
                                   # Default is catalog.

#check_unlogged_table = on
                                   # If on, enable unlogged table check in SELECT statements.
                                   # This initiates queries against system catalog of primary/main
                                   # thus increases load of primary.
                                   # If you are absolutely sure that your system never uses unlogged tables
                                   # and you want to save access to primary/main, you could turn this off.
                                   # Default is on.
#enable_shared_relcache = on
                                   # If on, relation cache stored in memory cache,
                                   # the cache is shared among child process.
                                   # Default is on.
                                   # (change requires restart)

#relcache_query_target = primary
                                   # Target node to send relcache queries. Default is primary node.
                                   # If load_balance_node is specified, queries will be sent to load balance node.
#------------------------------------------------------------------------------
# IN MEMORY QUERY MEMORY CACHE
#------------------------------------------------------------------------------
#memory_cache_enabled = off
                                   # If on, use the memory cache functionality, off by default
                                   # (change requires restart)
#memqcache_method = 'shmem'
                                   # Cache storage method. either 'shmem'(shared memory) or
                                   # 'memcached'. 'shmem' by default
                                   # (change requires restart)
#memqcache_memcached_host = 'localhost'
                                   # Memcached host name or IP address. Mandatory if
                                   # memqcache_method = 'memcached'.
                                   # Defaults to localhost.
                                   # (change requires restart)
#memqcache_memcached_port = 11211
                                   # Memcached port number. Mondatory if memqcache_method = 'memcached'.
                                   # Defaults to 11211.
                                   # (change requires restart)
#memqcache_total_size = 64MB
                                   # Total memory size in bytes for storing memory cache.
                                   # Mandatory if memqcache_method = 'shmem'.
                                   # Defaults to 64MB.
                                   # (change requires restart)
#memqcache_max_num_cache = 1000000
                                   # Total number of cache entries. Mandatory
                                   # if memqcache_method = 'shmem'.
                                   # Each cache entry consumes 48 bytes on shared memory.
                                   # Defaults to 1,000,000(45.8MB).
                                   # (change requires restart)
#memqcache_expire = 0
                                   # Memory cache entry life time specified in seconds.
                                   # 0 means infinite life time. 0 by default.
                                   # (change requires restart)
#memqcache_auto_cache_invalidation = on
                                   # If on, invalidation of query cache is triggered by corresponding
                                   # DDL/DML/DCL(and memqcache_expire).  If off, it is only triggered
                                   # by memqcache_expire.  on by default.
                                   # (change requires restart)
#memqcache_maxcache = 400kB
                                   # Maximum SELECT result size in bytes.
                                   # Must be smaller than memqcache_cache_block_size. Defaults to 400KB.
                                   # (change requires restart)
#memqcache_cache_block_size = 1MB
                                   # Cache block size in bytes. Mandatory if memqcache_method = 'shmem'.
                                   # Defaults to 1MB.
                                   # (change requires restart)
#memqcache_oiddir = '/var/log/pgpool/oiddir'
                                   # Temporary work directory to record table oids
                                   # (change requires restart)
#cache_safe_memqcache_table_list = ''
                                   # Comma separated list of table names to memcache
                                   # that don't write to database
                                   # Regexp are accepted
#cache_unsafe_memqcache_table_list = ''
                                   # Comma separated list of table names not to memcache
                                   # that don't write to database
                                   # Regexp are accepted
pgpool.conf (54,353 bytes)   

Issue History

Date Modified Username Field Change
2023-09-28 18:20 philB New Issue
2023-09-28 18:20 philB File Added: pgpool-TueNEW.log
2023-10-03 14:42 pengbo Note Added: 0004434
2023-10-03 14:42 pengbo Assigned To => pengbo
2023-10-03 14:42 pengbo Status new => feedback
2023-10-03 16:33 philB Note Added: 0004436
2023-10-03 16:33 philB File Added: pgpool.conf
2023-10-03 16:33 philB Status feedback => assigned