SLONIK_DROP_SET(7)

πŸ“¦
version 2.2.11 Β· 4 versions
, in debian trixie, ubuntu questing

πŸ’– DROP SET β€” bestie, we're deleting a whole set πŸ’–

okay so this is a page from the Slony-I 2.2.11 Documentation era, and it's the slonik_drop_set(7) manual β€” yes, that slonik. buckle up πŸŽ€


✨ NAME ✨

DROP SET β€” discard a Slony-I replication set. like, bye girl, we're letting it go πŸ’…


🌸 SYNOPSIS 🌸

DROP SET (options);

πŸ¦‹ DESCRIPTION πŸ¦‹

So what we're doing here is dropping a set of tables out of the Slony-I configuration. And the way that this works? It automatically unsubscribes every single node from the set β€” no manual unsubscribing, no "wait should I do that myself", it just handles it β€” and it restores the original triggers and rules on all the subscribers. giving cleanup crew energy fr fr 🧹✨

Now here's the deets on the two things you can pass in:

  • ID = ival β€” the ID of the set that's getting dropped. that's the one you're saying goodbye to 🫢
  • ORIGIN = ival β€” the current origin node of the set. yes, current, like right now, not whatever it used to be πŸ‘‘

This whole thing runs through schemadocdropset(p_set_id integer) β€” and ngl, that one is [not available as a man page]. so if you went looking for it, that's why, bestie, it's just not there 😭


πŸŽ€ EXAMPLE πŸŽ€

look at her go:

  DROP SET ( ID = 5,
             ORIGIN = 2 );

that's it. that's the whole vibe. set 5, origin node 2, dropped. slay.


πŸ”₯ LOCKING BEHAVIOUR πŸ”₯

heads up, this is the part where things get a lil intense

On each node, this is going to require taking out exclusive locks on every replicated table in the set. why? because it has to modify the table schema to clean up all the triggers and rules. so yeah β€” exclusive locks, every replicated table, every node. it's giving "clear your schedule" πŸ’€ not a background-task-at-3pm situation.


⭐ SLONIK EVENT CONFIRMATION BEHAVIOUR ⭐

Here's the lil synchronization moment: slonik waits for the command that was submitted to the previous event node to be confirmed on the specified event node before it even thinks about submitting this command. it's patient. it's polite. it's not skipping the line 🫢


🌈 VERSION INFORMATION 🌈

This command was introduced in Slony-I 1.0 β€” so it's basically an OG. iconic behavior, honestly πŸ‘‘


that's the whole page bestie, you're officially certified in dropping sets πŸ’– and this cutie lil doc was brought to you by the fine folks behind Slony-I 2.2.11 Documentation, dated 19 September 2024 β€” mwah, thanks for the lore πŸŽ€πŸ’œ

πŸ“¦ where this page comes from