Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gZo0b-0000Dl-Hs for pgsql-admin@arkaria.postgresql.org; Thu, 20 Dec 2018 02:24:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gZo0Z-00082T-4P for pgsql-admin@arkaria.postgresql.org; Thu, 20 Dec 2018 02:24:19 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gZo0Y-00082M-Qb for pgsql-admin@lists.postgresql.org; Thu, 20 Dec 2018 02:24:18 +0000 Received: from mail-oi1-x22c.google.com ([2607:f8b0:4864:20::22c]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gZo0R-0003oY-1Y for pgsql-admin@lists.postgresql.org; Thu, 20 Dec 2018 02:24:17 +0000 Received: by mail-oi1-x22c.google.com with SMTP id u18so151381oie.10 for ; Wed, 19 Dec 2018 18:24:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=xZGbqKmLToDTfSst8EiSEIk4lZKNuOYfxJnC6hS7Ad0=; b=KSu4/LfBXhKDzgFwEbyA9284dJ+guNTBuu+NsizlE8bgOnyDI3lnXFmjVptqciBY1F E7LQDQv2th1QOjnAnWxtdYg3l1qAw0cbHlfIOlKZlc6OIVe4VOBdrFyUMdefKraMaAOQ ch154VeGH1+OrZ00eR2RtXsl4KfBQXMxISC45DCmmWcESAN6dzOeFX1EgmRXLQUxLkZL LQq0V5qBtGCiNbx4v8DotgGHEjJudxuayssM5c70LG/x1J3fD3Ch6pKkZutUJunfWiQx KXN3N+iSSTPC4mCU+l5UMpUmy2YojqT+7zP/5t5OhpV7W5iRHfd6WPx/u4b4HUfBJYrA Knyw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=xZGbqKmLToDTfSst8EiSEIk4lZKNuOYfxJnC6hS7Ad0=; b=Yn6WZ5d/MuWrX7Ga835tKO/741vGn9cCWn47ysYAF1x/kqsURllsQV5jbFTe2ch1Gd 8uRXDMuoAArWrEfc0+6qu1OyC8muTHa4Rplh6N5hpjFQNs+K0TNSsDGwQ6y3vMkvczHT HAeesaZWiuPwnW+p8V9j5aqO7XubIMPgmOFjowlkF0q+TdWwTvCiLqh2w7bjB1FS6sad zHHxWpvsom2K5QRutI2TVbxvJHtHU9rEkV0DtZz3WbIiV3KTZQguh72V1u6AIFp8qKDN XPC39kydEgV9CJSZxJOJ3LbREWGDZJxHMLwfMQqcD/OVmpjPqNqB15qr477N+KTyolzz 5CzA== X-Gm-Message-State: AA+aEWZmLUshvCHDPkwqROh6ycHMH9Jv+hXbFaYYOjQfAREAIkhPfiNv bu/uvhQ9awiP/+UsrmL+dWop5nCn X-Google-Smtp-Source: AFSGD/VMzbz9VWUip2DDKmao3JL4hDYqAEHD2wa69DYpcWnOs2aomFevFn0DJxbdAc0aNJ2GqZON+A== X-Received: by 2002:aca:5117:: with SMTP id f23mr841939oib.72.1545272648497; Wed, 19 Dec 2018 18:24:08 -0800 (PST) Received: from [192.168.1.10] (ip70-171-116-89.no.no.cox.net. [70.171.116.89]) by smtp.googlemail.com with ESMTPSA id q13sm9876244ota.14.2018.12.19.18.24.07 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Dec 2018 18:24:07 -0800 (PST) Subject: Re: Multi master implementation To: pgsql-admin@lists.postgresql.org References: From: Ron Message-ID: <0dd867f2-46d1-70f0-29b9-ac6db713cc38@gmail.com> Date: Wed, 19 Dec 2018 20:24:07 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------53D65BB6F27421071921EFC4" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------53D65BB6F27421071921EFC4 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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 > 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 >> -- Angular momentum makes the world go 'round. --------------53D65BB6F27421071921EFC4 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit 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.pathria@goevive.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

--
Angular momentum makes the world go 'round.
--------------53D65BB6F27421071921EFC4--