SLONIK_ADMIN_CONNINFO(7)

💖 NAME 💖

ADMIN CONNINFO — the lil preamble that tells slonik how to find a PostgreSQL database 🎀

---

✨ SYNOPSIS ✨

NODE ival ADMIN CONNINFO = 'DSN'; [ ival;] [ 'conninfo']

---

🌸 DESCRIPTION 🌸

Okay bestie, here's the tea ☕: this command describes how the slonik utility can actually reach a node's database in the cluster — and it does this from wherever slonik itself is being run (which, realistically, is the DBA's workstation, no cap).

That conninfo string? It's the string argument you hand straight to the PQconnectdb() libpq function. That's it, that's the whole vibe. 💅

Now here's a fun fact: slonik will not even try to connect to a given database unless some subsequent command actually requires that connection. Lowkey polite of it. 🦋

Note 💭 As mentioned in the original documents, Slony-I is designed as an enterprise replication system for data centers. It has been assumed throughout the entire development that the database servers and administrative workstations involved in replication and/or setup and configuration activities can use simple authentication schemes like 'trust'. Alternatively, libpq can read passwords from .pgpass.

Note 😭 If you need to change the DSN information for a node — as would happen if the IP address for a host were to change — you must submit the new information using the SLONIK STORE PATH(7) command, and that configuration will be propagated. Existing slon processes may need to be restarted in order to become aware of the configuration change. Not me having to restart things, the drama 🙈

---

🔥 EXAMPLE 🔥

NODE 1 ADMIN CONNINFO = 'dbname=testdb host=server1 user=slony';

---

👑 VERSION INFORMATION 👑

This command was introduced in Slony-I 1.0 — an OG, fr fr. ⭐

---

Slony-I 2.2.11 Documentation, dated 19 September 2024 — that's a wrap, bestie, go slay your replication setup 💜✨