Re: Master-slave failover question - Mailing list pgsql-novice

From Athanasios | ZenGuard
Subject Re: Master-slave failover question
Date
Msg-id CAHPc5uS-XGfRr5i4ELrcWxSV2e12d_crF=QX9rXgZ2Y3svOKpg@mail.gmail.com
Whole thread Raw
In response to Re: Master-slave failover question  ("Athanasios | ZenGuard" <athanasios@zenguard.org>)
Responses Re: Master-slave failover question
List pgsql-novice
Hi all again,
I rigged up a solution with PGPool (!) in master-slave mode, using the existing documentation and it works like a charm with a downtime of only a few seconds, which is acceptable in our case. However assume the following scenario:
1) Master goes down
2) slave gets promoted to master
owing to the usage of pgpool, this works fine. However, assuming that there is a certain amount of write traffic that goes to the new master. When the old master (sorry for the terminology) comes back up, how can I "sync" him with all the changes that have been performed? This is one of the two pieces of the puzzle missing for me (the other one is pgpool specific and I directed my query to their specific mailing list).
Thanks for any replies.


On Fri, Jan 3, 2014 at 2:00 PM, Athanasios | ZenGuard <athanasios@zenguard.org> wrote:
Hi,
PGPool is a bit of a blackbox. I am confident in the use of VRRP but I have not seen any documentation on how to combine this with pgpool to eliminate single points of failure.
Can you share a few more details about how I can use a virtual IP?


On Fri, Jan 3, 2014 at 1:12 PM, Sameer Kumar <sameer.kumar@ashnik.com> wrote:

Check their site. Www.enterprisedb.com

Can you share you failover command here? You may use ifconfig to switch a vitrual IP while doing a failover.

BTW why are you reluctant to use pgpool?

Regards
Sameer

PS: Sent from my Mobile device. Pls ignore typo n abb



pgsql-novice by date:

Previous
From: "Athanasios | ZenGuard"
Date:
Subject: Re: Master-slave failover question
Next
From: Sameer Kumar
Date:
Subject: Re: Master-slave failover question