SLONIK_SET_ADD_SEQUENCE(7)

💖 NAME 💖

SET ADD SEQUENCE — bestie, this is the Slonik command that adds a sequence to a Slony-I replication set. That's it, that's the whole job. ✨

This page lives in the Slony-I 2.2.11 Documentation collection, and it's giving very much "here's how you get a sequence into the club." 🎀

---

🌸 SYNOPSIS 🌸

SET ADD SEQUENCE (options);

---

✨ DESCRIPTION ✨

Okay so real talk: this command takes an existing user sequence and adds it to a replication set. Lowkey the one catch — the set can't currently be subscribed by any other node. That whole "already got subscribers" situation? That's handled by the SLONIK MERGE SET(7) command instead. Different tool, different vibe. 💅

Now let's meet the options, because there are several and they all matter:

• SET ID = ival — the ID of the set that the sequence is getting added to.
• ORIGIN = ival — the origin node for the set. This one is optional, iykyk.
• ID = ival — the unique ID of the sequence.

Heads up bestie: this ID needs to be unique across sequences throughout the cluster. The numbering of tables is separate, so you could have a table with ID 20 and a sequence with ID 20 and they'd be recognized as totally separate entities. No cap, they do not collide. 🫶

• This parameter is optional. If this parameter is omitted then slonik will check every node that it can connect to and find the highest table id being used across all nodes.
• FULLY QUALIFIED NAME = 'string' — the full sequence name, schema name included. If SEQUENCES is specified then FULLY QUALIFIED NAME should be omitted. Pick a lane, babe. 🌈
• SEQUENCES = 'string' — a POSIX regular expression that matches the sequences that should be added to the replication set. This regular expression is passed to postgresql for evaluation on the set origin against fully qualified sequence names. This parameter is optional. If FULLY QUALIFIED NAME is omitted then SEQUENCES must be specified.
• COMMENT = 'string' — a descriptive text added to the sequence entry. Give it a lil caption, she deserves one. 💜

Under the hood this uses schemadocsetaddsequence(p_seq_comment integer, p_fqname integer, p_seq_id text, p_set_id text) [not available as a man page]. Iconic function signature, honestly. 😭

---

🦋 EXAMPLE 🦋

Here's the fully-specified era:

     SET ADD SEQUENCE (
     SET ID = 1,
     ORIGIN = 1,
     ID = 20,
     FULLY QUALIFIED NAME = 'public.tracker_ticket_id_seq',
     COMMENT = 'Support ticket ID sequence'
     );

or, the regex girlies' route:

      SET ADD SEQUENCE(
      SET ID=1,
      SEQUENCES='public\\.tracker_ticket_id_seq'
      );

---

🔒 LOCKING BEHAVIOUR 🔒

No application-visible locking should take place. Zero drama, zero locks, we love a chill command. 😌

---

⏳ 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. She's patient. She's polite. She waits her turn. 👑

---

⭐ VERSION INFORMATION ⭐

This command was introduced in Slony-I 1.0 — an elder, a legend, a founding mother. 💖

---

And that's the whole page, bestie! This was Slony-I 2.2.11 Documentation, dated 19 September 2024 — go forth and replicate those sequences responsibly. Mwah. 💅✨🎀