From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Multi master implementation |
Date: | 2018-12-20 02:24:07 |
Message-ID: | 0dd867f2-46d1-70f0-29b9-ac6db713cc38@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I think he wants masters *and* slaves.
On 12/19/18 8:00 PM, soumitra bhandary wrote:
> Hi Prince,
>
> BDR is something which is not that much robust as conventional master
> slave replication.
>
> Why do you want master node in DR set up ?
> Do you want to enable simultaneous write operations at DR site as well??
> Normally DR setups remain in cascade replication from one of the stand by
> node at production side .
>
> Sent from my iPhone
>
> On 19-Dec-2018, at 11:55 PM, Prince Pathria <prince(dot)pathria(at)goevive(dot)com
> <mailto:prince(dot)pathria(at)goevive(dot)com>> wrote:
>
>> Hi,
>>
>> I want to how people are implementing multi master architecture in
>> Postgres. For now, I've come across BDR3 and bucardo for multimaster
>> approach.
>>
>> Though both doesn't seem to be much promising to me.
>>
>> Goal: 2 master and their 3 slaves. [1 master + 2 slaves] in production
>> site and [1 master + 1 slave]
>> in DR site.
>>
>> Can you guys share how you did it and what issues did you faced?
>>
>> Thanks in advance!
>>
>> Happy to help :)
>> Prince Pathria Systems Architect Intern Evive +91 9478670472 goevive.com
>> <http://goevive.com>
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Devendra Yadav | 2018-12-20 03:09:00 | Stats getting corrupted |
Previous Message | soumitra bhandary | 2018-12-20 02:00:53 | Re: Multi master implementation |