From: | Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com> |
---|---|
To: | MichaelDBA <MichaelDBA(at)sqlexec(dot)com> |
Cc: | Holger Jakobs <holger(at)jakobs(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org, Firthouse banu <penguinsfairy(at)gmail(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Re: |
Date: | 2021-11-24 17:49:59 |
Message-ID: | CANbhV-FLDLmYnAGPNMkpqU1S-Yx2wPQyBhpf3HQbQ0TxATVceA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Wed, 24 Nov 2021 at 17:38, MichaelDBA <MichaelDBA(at)sqlexec(dot)com> wrote:
>
> Oh really? BDR is acid-compliant? How can it be without a global lock manager to control access to resources and a consistent view of data and enforce isolation levels?
Many types of distributed system offer consistency. Very few use a
global lock manager, so this is not a requirement.
> Please explain the magic.
Anyone interested to know more can start here:
https://www.enterprisedb.com/products/bidirectional-replication-bdr-postgresql-database
--
Simon Riggs http://www.EnterpriseDB.com/
From | Date | Subject | |
---|---|---|---|
Next Message | MichaelDBA | 2021-11-24 18:18:40 | Re: Re: Re: |
Previous Message | MichaelDBA | 2021-11-24 17:38:00 | Re: Re: |