SLONIK_UNLOCK_SET(7)

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

✨ SLONIK_UNLOCK_SET ✨

okay bestie, so this is the Slony-I man page for UNLOCK SET β€” aka the command that unlocks a Slony-I set that was locked. it's in the SLONIK family (section 7, if you're keeping track πŸ’…). no cap, this one's short and sweet, so let's gooo πŸ¦‹


πŸ’– NAME πŸ’–

UNLOCK SET β€” Unlock a Slony-I set that was locked πŸŽ€


🌸 SYNOPSIS 🌸

UNLOCK SET (options);

✨ DESCRIPTION ✨

Unlocks a previously locked set. that's literally it, she does one thing and she does it well πŸ‘‘

ID = ival : ID of the set to unlock πŸ”“

ORIGIN = ival : Node ID of the current set origin 🌐

under the hood, this uses schemadocunlockset(p_set_id integer) β€” and nope, that one is not available as a man page, so don't go looking for it πŸ™ˆ


🧚 EXAMPLE 🧚

UNLOCK SET (
   ID = 1,
   ORIGIN = 3
);

look at her go, so clean, so iconic ⭐


πŸ”’ LOCKING BEHAVIOUR πŸ”’

Exclusive locks on each replicated table will be taken out on the origin node, as the triggers are removed from each table that reject table updates.

so like, real talk: exclusive locks + triggers getting yeeted off every table that rejects table updates. that's the whole vibe. πŸ’€

πŸ“£ SLONIK EVENT CONFIRMATION BEHAVIOUR πŸ“£

Slonik does not wait for event confirmations before performing this command.

fr fr, it just sends it and moves on. no waiting, no checking in, main character energy only 🌈

πŸ•°οΈ VERSION INFORMATION πŸ•°οΈ

This command was introduced in Slony-I 1.0 β€” an OG, basically. πŸ‘‘


and that's the whole page, bestie!! 🌸 this gorgeous little doc comes from Slony-I 2.2.11 Documentation, dated 19 September 2024, and it lives in section 7 of the manual. mwah, take care, go unlock that set, ily πŸ«ΆπŸ’–βœ¨

πŸ“¦ where this page comes from