From: | Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com> |
---|---|
To: | Holger Jakobs <holger(at)jakobs(dot)com> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org, MichaelDBA <MichaelDBA(at)sqlexec(dot)com>, Firthouse banu <penguinsfairy(at)gmail(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: |
Date: | 2021-11-24 17:11:20 |
Message-ID: | CANbhV-EgEMD9QNFa+FS33CeMvbLr+xXMQ4J5civoOfntFq6mLg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Wed, 24 Nov 2021 at 17:08, Holger Jakobs <holger(at)jakobs(dot)com> wrote:
>
> Am 24. November 2021 18:06:45 MEZ schrieb Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>:
> >On Wed, 24 Nov 2021 at 14:03, MichaelDBA <MichaelDBA(at)sqlexec(dot)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?
Yes, I read that, which is why I didn't reply to the OP.
My response was to the statement about "multi-master replication".
> Of course, BDR3 is a great tool.
--
Simon Riggs http://www.EnterpriseDB.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2021-11-24 17:21:24 | Re: |
Previous Message | Holger Jakobs | 2021-11-24 17:08:42 | Re: |