---
name: "SLONIK_SET_MOVE_SEQUENCE"
section: "7"
platform: "linux"
package: "slony1-2-doc"
version: "2.2.11-6"
release: "Debian 13 (Trixie)"
platforms: ["linux"]
url: "https://new.carta.tech/SLONIK_SET_MOVE_SEQUENCE"
---

# SLONIK\_SET\_MOVE\_SEQUENCE(7)

Move a sequence from one Slony-I replication set to another

## NAME

SET MOVE SEQUENCE - Move a sequence from one Slony-I replication set to another

## SYNOPSIS

FC**SET MOVE SEQUENCE (options);**F\[0\]

## DESCRIPTION

Change the set a sequence belongs to. The current set and the new set must originate on the same node and subscribed by the same nodes.

**Caution**

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 sequences. Moving a sequence too early to a new set causes the subscriber to try and add the sequence already during the subscription process, which fails with a duplicate key error and breaks replication.

- FCORIGIN = ival F\[0\]

  Origin node for the set. A future version of slonik might figure out this information by itself.

- FCID = ival F\[0\]

  Unique ID of the sequence.

- FCNEW SET = ival F\[0\]

  Unique ID of the set to which the sequence should be moved.

This uses “schemadocsetmovesequence(p\_new\_set\_id integer, p\_seq\_id integer)” \[not available as a man page\].

## EXAMPLE

```
FCSET MOVE SEQUENCE (
    ORIGIN = 1,
    ID = 20,
    NEW SET = 3
);
    F[0]
```

## LOCKING BEHAVIOUR

No application-visible locking should take place.

## SLONIK EVENT CONFIRMATION BEHAVIOUR

Slonik waits for the command submitted to the previous event node to be confirmed on the specified event node before submitting this command.

## VERSION INFORMATION

This command was introduced in Slony-I 1.0.5