| From: | Holger Jakobs <holger(at)jakobs(dot)com> |
|---|---|
| To: | pgsql-admin(at)lists(dot)postgresql(dot)org, Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>, MichaelDBA <MichaelDBA(at)sqlexec(dot)com> |
| Cc: | Firthouse banu <penguinsfairy(at)gmail(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: |
| Date: | 2021-11-24 17:08:42 |
| Message-ID: | 0ED6B91F-C228-404F-A4F2-B9532E205B2D@jakobs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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?
Of course, BDR3 is a great tool.
--
Holger Jakobs, Bergisch Gladbach
+49 178 9759012
- sent from mobile, therefore short -
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2021-11-24 17:11:20 | Re: |
| Previous Message | Simon Riggs | 2021-11-24 17:06:45 | Re: |