[pgpool-general: 5622] Re: pgpool 3.6.4 failover - failover scenario question

Avi Weinberg AviW at gilat.com
Sun Jul 16 15:23:05 JST 2017


We also have problems with failovers when postgres and pgpool are on the same machine.  If there are configuration parameters that can be changed to improve the failover mechanism I will also be happy to hear.


From: pgpool-general-bounces at pgpool.net [mailto:pgpool-general-bounces at pgpool.net] On Behalf Of Shay Cohavi
Sent: Friday, July 14, 2017 7:57 PM
To: pgpool-general at pgpool.net
Subject: [pgpool-general: 5621] pgpool 3.6.4 failover - failover scenario question

I have 2 postgres servers (postgres 9.3.5) installed with pgpool(3.6.4) on the same node.

server 2
pgpool vip


# psql -U postgres -h -p 9999 -c 'show pool_nodes'
 node_id |   hostname    | port | status | lb_weight |  role   | select_cnt | load_balance_node | replication_delay
 0       | | 5432 | up     | 0.500000  | primary | 3718       | true              | 0
 1       | | 5432 | up     | 0.500000  | standby | 0          | false             | 0

my question is about disaster recovery scenario:

1. "primary postgres" and the "master pgpool" is on server1 . pgpool vip established on this node (

2. server1 went down due to  power break. (server1 is dead!!!)

3. pgpool on server server2 get promoted (vip established .

4. NO postgres failover action occurs by the pgpool. pgpool keeps searching for primary postgres with no success.

should the new master pgpool execute an failover action(promote) to the slave postgres ??

IMPORTANT - This email and any attachments is intended for the above named addressee(s), and may contain information which is confidential or privileged. If you are not the intended recipient, please inform the sender immediately and delete this email: you should not copy or use this e-mail for any purpose nor disclose its contents to any person.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20170716/6ad8ee5e/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 16223 bytes
Desc: image001.jpg
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20170716/6ad8ee5e/attachment-0001.jpg>

More information about the pgpool-general mailing list