Dmitry Yemanov wrote 27.10.2021 9:18:
Nope, it's configured on the replica side and allows the received changes to be propagated further (if replica is also configured as a primary, i.e. A->B->C).
...and must be disabled for replication A->B->A i.e. bidirectional to prevent infinite data bouncing.
-- WBR, SD. Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
