From: MichaelDBA <MichaelDBA@sqlexec.com>
To: Simon Riggs <simon.riggs@enterprisedb.com>
Cc: Scott Ribe <scott_ribe@elevated-dev.com>
Cc: Firthouse banu <penguinsfairy@gmail.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Re:
Date: Wed, 24 Nov 2021 12:33:08 -0500
Message-ID: <e6222927-b6b3-56ce-c555-028afe790f86@sqlexec.com> (raw)
In-Reply-To: <CANbhV-Fg93Yo6QSdYhGvVHE0QSOfvK8jSOP8vOV019B8=Gr8LA@mail.gmail.com>
References: <CAK_Ha4yABYGEGAMzfNJaxeepeQNFRTFaqYRsns3GCPFeQWEWhQ@mail.gmail.com>
<BD718062-F117-4C56-B678-1CF872855402@elevated-dev.com>
<CANbhV-Fg93Yo6QSdYhGvVHE0QSOfvK8jSOP8vOV019B8=Gr8LA@mail.gmail.com>
Unfortunately, it should be stated that BDR is not open source. You
have to be a EnterpriseDB customer to get it. I think this applies to
BDR versions 2 and 3. I think only version 1 is truly open source at
this point.
Simon Riggs wrote on 11/24/2021 12:21 PM:
> On Wed, 24 Nov 2021 at 14:17, Scott Ribe <scott_ribe@elevated-dev.com> wrote:
>>> On Nov 24, 2021, at 2:18 AM, Firthouse banu <penguinsfairy@gmail.com> wrote:
>>>
>>> Please do let me know best tool for this I have 5 servers all should be in sync with data.
>> Have you analyzed what data conflicts will occur and how to resolve them?
> Which makes it sound like a problem exists, so I think some additional
> information is needed for a balanced assessment.
>
> BDR has facilities that allow you to find out whether any conflicts
> occur for an application, so it is easy to assess this. Conflicts that
> do occur are resolved automatically using programmable rules, yet
> logged for later assessment. Data quality tools allow you to confirm
> no anomalies exist in realtime.
>
> Any conflicts that occur would be as a result of 1) data access
> patterns, 2) choice of consistency, 3) how transactions are routed to
> nodes. It isn't random and many applications are naturally conflict
> free, even with randomly routed transactions.
>
> If you use BDR using the AlwaysOn architecture then all transactions
> are routed via a single node and no conflicts occur in normal running.
> Depending on how failover is achieved, there may be a small window for
> conflicts.
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: MichaelDBA@sqlexec.com, simon.riggs@enterprisedb.com, scott_ribe@elevated-dev.com, penguinsfairy@gmail.com
Subject: Re: Re:
In-Reply-To: <e6222927-b6b3-56ce-c555-028afe790f86@sqlexec.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox