SLONIK_SYNC(7)

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

✨ SYNC ✨

okay bestie, so this is a page from the Slony-I docs β€” specifically the SLONIK SYNC(7) page β€” and it's genuinely short and sweet, so let's get into it πŸ’–


🌸 NAME 🌸

SYNC β€” generate an ordinary SYNC event. that's it, that's the whole job 🫢


πŸŽ€ SYNOPSIS πŸŽ€

SYNC (options);

πŸ’… DESCRIPTION πŸ’…

It generates a SYNC event on a specified node. simple as that, no cap ✨

🌈 OPTIONS 🌈

  • ID = ival β€” the node on which to generate the SYNC event. that's the one and only thing you're picking here, bestie πŸ‘‘

πŸ¦‹ EXAMPLE πŸ¦‹

here's what it looks like in the wild, literally copy-paste energy:

SYNC (ID = 1);
WAIT FOR EVENT (ORIGIN = 1, CONFIRMED = 2, WAIT ON=1);

so you fire the SYNC off on node 1, and then you go wait on the event β€” ORIGIN = 1, CONFIRMED = 2, WAIT ON=1. iconic little duo fr fr πŸ”₯


πŸ”’ LOCKING BEHAVIOUR πŸ”’

No application-visible locking should take place. so like… nothing your app can see gets locked up. go off, no blocking drama πŸ’€βœ¨


⭐ SLONIK EVENT CONFIRMATION BEHAVIOUR ⭐

Slonik does not wait for event confirmations before performing this command. so it just does the thing and moves on, main character energy, no waiting around for the group chat to reply πŸ˜­πŸ’…

lowkey important: if you need to actually know the event landed, that's what the WAIT FOR EVENT line in the example is for. Slonik itself is not gonna hold your hand here.

πŸ‘‘ VERSION INFORMATION πŸ‘‘

This command was introduced in Slony-I 1.1.6 / 1.2.1 β€” so it's been around a minute, a true veteran πŸŽ€


and that's the whole page!! this was documented in the Slony-I 2.2.11 Documentation, dated 19 September 2024 β€” mwah, slay, bye bestie πŸ’–πŸ§šπŸŒΈ

πŸ“¦ where this page comes from