SLONIK_UNINSTALL_NODE(7)

✨ SLONIK UNINSTALL NODE ✨

okay bestie, we're deep in the Slony-I 2.2.11 docs now and this one is SLONIK UNINSTALL NODE(7) — the man page that tells you how to gently, lovingly decommission a Slony-I node. no cap, it's giving "we're breaking up but I'm keeping the furniture" 💅

---

🌸 NAME 🌸

UNINSTALL NODE — Decommission Slony-I node 🫶

---

🎀 SYNOPSIS 🎀

UNINSTALL NODE (options);

---

🦋 DESCRIPTION 🦋

So here's the vibe: this puts all your tables back into the unlocked state, with all the original user triggers, constraints and rules restored. Any Slony-I-specific serial key columns that got added? Dropped. The Slony-I schema itself? Also dropped. 🧹✨

The node becomes a standalone database. And the data? The data is left untouched, bestie — nobody is touching your data, we would never. 🙈

the options, one at a time

• ID = ival — Node ID of the node you wanna uninstall. that's the one.

---

This whole thing uses “schemadocuninstallnode()” [not available as a man page]. lowkey iconic of it.

---

the difference between UNINSTALL NODE and DROP NODE — this is the part people get confused about, so listen up. All UNINSTALL NODE does is remove the Slony-I configuration. It does not drop the node's configuration from replication. that's it, that's the difference, periodt. 💅

---

💖 EXAMPLE 💖

  UNINSTALL NODE ( ID = 2 );

look at her go ✨

---

🔒 LOCKING BEHAVIOUR 🔒

When it's dropping triggers off of application tables, this is gonna require exclusive access to each replicated table on the node being discarded. so like, heads up, nobody else can be in there touching those tables while this happens. exclusive means exclusive, fr fr. 👑

---

💀 DANGEROUS/UNINTUITIVE BEHAVIOUR 💀

okay this is the scary part, buckle up:

If you're using connections that cache query plans (and ngl this is particularly common for Java application frameworks with connection pools 😭), those connections may cache query plans that include the pre-UNINSTALL NODE state of things. Which means you'll get error messages about missing OIDs — specifically “[MISSING TEXT]” [not available as a man page].

⚠️ After dropping a node, you may also need to recycle connections in your application. do not skip this step, I'm begging you 🙏

---

⭐ SLONIK EVENT CONFIRMATION BEHAVIOUR ⭐

Slonik does not wait for event confirmations before performing this command. it just goes. main character energy, honestly. 🌈

---

👑 VERSION INFORMATION 👑

This command was introduced in Slony-I 1.0. a legend from the start, we love to see it. 💜

---

and that's the whole page, bestie — written up on 19 September 2024, straight outta the Slony-I 2.2.11 Documentation set. go forth and uninstall responsibly 🦋💖✨