On 31 August 2016 at 22:38, Salvatore Tomaselli
<salvatore.tomaselli@cryptzone.com> wrote:
> Hello,
>
> I have been looking around in the documentation and I didn't find anything, so I wonder if there is support in bdr
forhaving transactions that happen while the global lock is acquired and get replicated everywhere before the
transactionends.
>
> Is there a way to achieve this?
The purpose of the global DDL lock to to prevent that.
If you ALTER a table on one node, say by ALTERing the type of a
column, while you continue to do write transactions to that table on
other nodes, when the other nodes' data replicates to the node that
does the DROP it won't make sense anymore. What value should be in the
new column?
BDR 1.0 adds a weaker DDL lock mode that is used for types of DDL
where that is not a concern. It only blocks other concurrent DDL. But
for DDL that alters tables it's necessary to block concurrent DML.
BTW, now that it's clear in-core logical replication is going in
another direction there's now a bdr-list@2ndquadrant.com mailing list;
see https://groups.google.com/a/2ndquadrant.com/forum/#!forum/bdr-list
.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
