SLONIK_DROP_LISTEN(7)

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

πŸ’– SLONIK_DROP_LISTEN(7) πŸ’–

okay bestie, welcome to the DROP LISTEN page β€” yes it's a real manual page, section 7, and yes we're gonna make it cute. this is from the Slony-I 2.2.11 Documentation era, so buckle up πŸŽ€


✨ NAME ✨

DROP LISTEN β€” bestie, this deletes the config that tells a Slony-I node how it listens for events. like, the whole "how do i hear about stuff" setup? gone. πŸ’…


🌸 SYNOPSIS 🌸

DROP LISTEN (options);

πŸ¦‹ DESCRIPTION πŸ¦‹

it removes a 'listen' configuration entry. that's it, that's the vibe. bye bye listener config 🫢

now here's the options, no skipping, every single one:

  • ORIGIN = ival β€” the Node ID of the event origin that the receiver is listening for. it's giving "who are the events coming from originally" πŸ‘‘
  • PROVIDER = ival β€” the Node ID of the node the receiver actually gets its events from, for events that originate at the origin. if you don't specify it, the default is just the origin. so like, no provider = provider is the origin, lowkey convenient ✨
  • RECEIVER = ival β€” the ID of the node receiving the events. the one with its ears perked up πŸ’–

under the hood this calls schemadocdroplisten(p_li_receiver integer, p_li_provider integer, p_li_origin integer) β€” and ngl, that one is not available as a man page. we only have the vibe, not the page πŸ™ˆ


🌈 EXAMPLE 🌈

DROP LISTEN ( ORIGIN = 1, RECEIVER = 2, PROVIDER = 3 );

look at that. clean. iconic. origin 1, receiver 2, provider 3. slay ⭐


πŸ”’ LOCKING BEHAVIOUR πŸ”’

no application-visible locking should take place. so like, nothing you'd notice, nothing to worry about, no drama πŸ’€βœ¨


πŸ”₯ SLONIK EVENT CONFIRMATION BEHAVIOUR πŸ”₯

okay this part matters, bestie: slonik waits for the command that was submitted to the previous event node to be confirmed on the specified event node before it submits this command. so it's polite. it waits its turn. main character energy but considerate 🫢


⏳ VERSION INFORMATION ⏳

  • this command was introduced in Slony-I 1.0 πŸŽ€
  • but as of version 1.1, you should not need to use it anymore. so... it's kinda giving legacy. still here though, still documented, still valid πŸ’œ
heads up bestie: that "you shouldn't need it anymore" line is straight from the source, not me being shady. the command still exists, it's just old news since 1.1 🌸

and that's the page!! mwah πŸ’‹ this was Slony-I 2.2.11 Documentation, dated 19 September 2024 β€” go forth and not need to drop your listens, iykyk πŸ§šπŸ’–

πŸ“¦ where this page comes from