Description
In the edb-async-replic replication system,
replicated tables are organized in sets. As a general rule of
thumb, a set should contain all the tables of one application,
that have relationships. In a well designed application, this is
equal to all the tables in one schema.
The smallest unit one node can subscribe for replication from
another node is a set. A set always has an origin. In
classical replication terms, that would be the "master."
Since in edb-async-replic a node can be the "master" over one set,
while receiving replication data in the "slave" role for
another at the same time, this terminology may easily become
misleading and should therefore be replaced with "set
origin" and "subscriber".
- ID = ival
ID of the set to be created.
- ORIGIN = ival
Initial origin node of the set.
- COMMENT = 'string'
A descriptive text added to the set entry.
