From: Holger Jakobs <holger@jakobs.com>
To: pgsql-admin@lists.postgresql.org, Simon Riggs <simon.riggs@enterprisedb.com>
To: MichaelDBA <MichaelDBA@sqlexec.com>
Cc: Firthouse banu <penguinsfairy@gmail.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re:
Date: Wed, 24 Nov 2021 18:08:42 +0100
Message-ID: <0ED6B91F-C228-404F-A4F2-B9532E205B2D@jakobs.com> (raw)
In-Reply-To: <CANbhV-G7piJpocze7Hu+NEUb5omzc59PxgyYmX0PSwsSZznvrA@mail.gmail.com>
References: <CAK_Ha4yABYGEGAMzfNJaxeepeQNFRTFaqYRsns3GCPFeQWEWhQ@mail.gmail.com>
<6cb32d43-75d1-b896-5267-48d75c536808@sqlexec.com>
<CANbhV-G7piJpocze7Hu+NEUb5omzc59PxgyYmX0PSwsSZznvrA@mail.gmail.com>
Am 24. November 2021 18:06:45 MEZ schrieb Simon Riggs <simon.riggs@enterprisedb.com>:
>On Wed, 24 Nov 2021 at 14:03, MichaelDBA <MichaelDBA@sqlexec.com> wrote:
>>
>> You do understand that multi-master replication is not acid-compliant
>> and the implications of that, right? It only works well for "read
>> globally, write locally" scenarios.
>
>This isn't true.
>
>Async multi-master has performance advantages, but some drawbacks. But
>systems such as BDR3 allow multiple modes of operation that overcome
>these perceived issues.
>
Are you aware that the original poster asked for open source solutions?
Of course, BDR3 is a great tool.
--
Holger Jakobs, Bergisch Gladbach
+49 178 9759012
- sent from mobile, therefore short -
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: holger@jakobs.com, simon.riggs@enterprisedb.com, MichaelDBA@sqlexec.com, penguinsfairy@gmail.com
Subject: Re:
In-Reply-To: <0ED6B91F-C228-404F-A4F2-B9532E205B2D@jakobs.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