[pgpool-general: 2356] Re: PGPool in HA Setup Question

[Mistina Michal]

Hi,

pacemaker can be a solution for you. However its not using VRRP. Maybe it
can - I don't know.

You can run pgpool process with the pgpool resource agent with combination
of virtual IP resource agent. If one host dies the resource agents boot
pgpool with virtual IP on the secondary host. If you would prefer
synchronized configuration files between hosts you can use DRBD.

 

Best regards,

Michal Mistina

 

From: pgpool-general-bounces at pgpool.net
[mailto:pgpool-general-bounces at pgpool.net] On Behalf Of Athanasios |
ZenGuard
Sent: Thursday, December 19, 2013 12:24 PM
To: pgpool-general at pgpool.net
Subject: [pgpool-general: 2349] PGPool in HA Setup Question

 

Dear list,

thanks of all thanks for all the hard work and the valuable support from the
PGPool community. I am using PGPool to do statement based replication
between 2 postgresql 9.3 databases. So far it works fine but pgpool by
itself is a single point of failure. My question is the following:

Is it possible to run 2 instances on pgpool on two different hosts and do an
active/passive failover scenario using VRRP? To elaborate a bit:

The 2 hosts share one virtual IP that is only active on one at a time. The
application points to that virtual IP, as opposed to the physical IP of one
of the two PGPool hosts. When one of the PGPools die, the other one grabs
the IP and continues to seamlessly serve connections towards the two
databases.

 

Is such a setup possible? If yes, has anyone implemented it in the past? Any
gotchas or pointers are more than welcome.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20131220/047c992b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2995 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20131220/047c992b/attachment-0001.p7s>