SLONIK_STORE_PATH(7)

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

πŸ’– SLONIK STORE PATH πŸ’–

okay bestie, this is SLONIK STORE PATH, page 7 of the Slony-I 2.2.11 docs, and it's literally the "how do these two nodes even talk to each other" page. it's giving matchmaker energy fr fr 🫢


✨ NAME ✨

STORE PATH β€” Configure Slony-I node connection 🌈


πŸŽ€ SYNOPSIS πŸŽ€

STORE PATH (options);

πŸ¦‹ DESCRIPTION πŸ¦‹

so basically this sets up how the replication daemon of one node connects to the database of another node. that's it, that's the whole vibe. πŸ’…

and if your replication system is supposed to use a special backbone network segment? bestie, THIS is the place where you drop in those special IP addresses or hostnames. and yeah β€” an existing configuration can be overwritten. no drama, it just gets replaced. πŸ”₯

the conninfo string must contain all the info you need to connect to the database as the replication superuser. like, all of it. no half-sending the info. πŸ‘‘

okay now this part matters so listen up: the names server and client have nothing to do with the particular role of a node within the cluster configuration. nothing!! it should simply be viewed as 'the server' has the message or data that 'the client is supposed to get.' that's the whole meaning. and for a simple 2 node setup, paths into both directions must be configured. both. don't skip one and then act surprised. πŸ™ˆ

also, it does not do any harm to configure path information from every node to every other node (full cross product). like, go off, be thorough. the connections are not established unless they are actually required to transfer events or confirmations because of listen entries, or data because of subscriptions. so it's lowkey free real estate. ✨

  • SERVER = ival β€” Node ID of the database to connect to. πŸ“
  • CLIENT = ival β€” Node ID of the replication daemon connecting. 🧚
  • CONNINFO = string β€” the PQconnectdb() argument used to establish the connection. πŸ”Œ
  • CONNRETRY = ival β€” number of seconds to wait before another attempt to connect is made in case the server is unavailable. default is 10. ⏳

this uses "schemadocstorepath(p_pa_connretry integer, p_pa_conninfo integer, p_pa_client text, p_pa_server integer)" [not available as a man page]. iykyk πŸ’€


🌸 EXAMPLE 🌸

STORE PATH ( SERVER = 1, CLIENT = 2,
             CONNINFO = 'dbname=testdb host=server1 user=slony'
           );

look at that. clean. iconic. πŸ‘‘


πŸ’œ LOCKING BEHAVIOUR πŸ’œ

No application-visible locking should take place. so like, nothing to worry about here, bestie. 🫢


⭐ SLONIK EVENT CONFIRMATION BEHAVIOUR ⭐

Slonik does not wait for event confirmations before performing this command. it just goes. main character energy, no waiting around. πŸ’…


🌈 VERSION INFORMATION 🌈

This command was introduced in Slony-I 1.0. so it's been here since the beginning, a true OG. πŸ‘‘


and that's the page!! brought to you by the Slony-I 2.2.11 Documentation era, dated 19 September 2024, filed under SLONIK STORE PATH(7). mwah, go configure those paths bestie πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from