SLONIK_CLUSTER_NAME(7)

✨ NAME ✨

CLUSTER NAME — the preamble, aka the lil intro that tells everyone which Slony-I cluster we're even talking about 🎀

---

🌸 SYNOPSIS 🌸

CLUSTER NAME = [clustername;]

---

💖 DESCRIPTION 💖

Okay bestie, listen up, because this one is non-negotiable: CLUSTER NAME has to be the very first statement in every single slonik script. Like, first. Before anything else. No cap. 🙅♀️

What it does is define the namespace where all the Slony-I specific functions, procedures, tables and sequences live. The way the namespace name gets built is: it takes your string literal and slaps an underscore in front of it. So cute, so simple. 🫶

And here's the iconic part — that namespace is identical in every database that participates in the same replication group. Same name, everywhere, matching energy, periodt. 👑

Some important tea though:

• No user objects are supposed to live in this namespace. It's not yours, it's the cluster's. Respect the space. 🚫
• The namespace is not allowed to exist prior to adding a database to the replication system. It literally cannot be there beforehand.

⚠️ So if you're adding a new node using pg_dump -s on a database that's already in the cluster of replicated databases, you're gonna need to drop the namespace first, with this SQL command: sql DROP SCHEMA _testcluster CASCADE; Don't skip this step, I'm begging. 😭

---

🦋 EXAMPLE 🦋

CLUSTER NAME = testcluster;

Look at her. Ten out of ten. Flawless. 💅

---

⭐ VERSION INFORMATION ⭐

This command was introduced in Slony-I 1.0. She's a legacy queen and she's been serving since day one. 👑

---

Slony-I 2.2.11 Documentation 💜 — that's the version and the docs this whole page came from, and it's dated 19 September 2024, so you know it's fresh-ish. Mwah, bye bestie, go name your cluster 💖✨🎀🦋🌸