Change the set a table belongs to. The current set and the new set must origin on the same node and subscribed by the same nodes.
Due to the way subscribing to new sets works make absolutely sure that the subscription of all nodes to the sets is completely processed before moving tables. Moving a table too early to a new set causes the subscriber to try and add the table already during the subscription process, which fails with a duplicate key error and breaks replication.
Current origin of the set. A future version of slonik might figure out this information by itself.
Unique ID of the table.
Unique ID of the set to which the table should be added.
This uses setmovetable(integer, integer).
If this was useful, let others know by an Affero rating