PG_AUTOCTL_GET_NODE_REPLICATION-QUORUM(1)

πŸ“¦
version 2.1 Β· 2 versions
, in fedora 43, fedora 44

πŸ’… pg_autoctl get node replication-quorum πŸ’…

okay bestie, so this is a page out of the pg_auto_failover manual, and honestly? it's a little cutie. it lives in the pg_autoctl family and it does exactly one (1) thing, but it does it flawlessly. no cap.


✨ NAME ✨

pg_autoctl get node replication-quorum β€” yeah that's the whole name, she's lowkey self-explanatory like that 🫢

also answers to: pg_autoctl get replication-quorum β€” which, bestie, is the way you ask the monitor for the replication-quorum property. same energy, slightly shorter name. iykyk.


🌸 SYNOPSIS 🌸

this command prints the pg_autoctl replication quorum for a given node. that's it, that's the vibe:

usage: pg_autoctl get node replication-quorum  [ --pgdata ] [ --json ] [ --formation ] [ --name ]

--pgdata      path to data directory
--formation   pg_auto_failover formation
--name        pg_auto_failover node name
--json        output data in the JSON format

look at her. four little flags. an icon πŸ‘‘


πŸ¦‹ DESCRIPTION πŸ¦‹

okay so that's the whole thing, and if you wanna see the full list of replication settings β€” like, the entire menu, not just this one dish β€” go peek at pg_autoctl show settings. that's the plug. πŸ’œ


✨ OPTIONS ✨

  • --pgdata β€” the location of the Postgres node that's being managed locally. if you don't say anything, she defaults to the environment variable PGDATA. and hey, if you'd rather connect to a monitor from anywhere instead of using the monitor URI that a local Postgres node managed with pg_autoctl is using β€” use --monitor for that. 🌈
  • --json β€” outputs the data all formatted in JSON. pretty, structured, machine-readable, we love her. ✨
  • --formation β€” shows replication settings for the given formation. defaults to default. yes bestie, default is the default, the most default to ever default. πŸŽ€
  • --name β€” shows replication settings for the given node, picked out by name. hi node, we see you. πŸ‘‹

πŸ’– ENVIRONMENT πŸ’–

  • PGDATA β€” Postgres directory location. you can use this instead of the --pgdata option. lowkey a shortcut, highkey valid.
  • PG_AUTOCTL_MONITOR β€” a Postgres URI to connect to the monitor node. can be used instead of the --monitor option. πŸ›°οΈ
  • XDG_CONFIG_HOME β€” the pg_autoctl command stores its configuration files in the standard place XDG_CONFIG_HOME. see the XDG Base Directory Specification. she's tidy like that.
  • XDG_DATA_HOME β€” the pg_autoctl command stores its internal states files in the standard place XDG_DATA_HOME, which defaults to ~/.local/share. see the XDG Base Directory Specification. a place for everything and everything in its place fr fr. 🧚

🌟 EXAMPLES 🌟

watch her work, bestie:

$ pg_autoctl get node replication-quorum --name node1
true

just true. no notes. slay. πŸ’…

and now with the JSON glow-up:

$ pg_autoctl get node replication-quorum --name node1 --json
{
    "name": "node1",
    "replication-quorum": true
}

ate and left no crumbs πŸ“


πŸ‘‘ AUTHOR πŸ‘‘

Microsoft


Copyright (c) Microsoft Corporation. All rights reserved.


real talk though bestie: everything above is exactly as written, no vibes-based guesses. don't invent flags, don't skip flags, just use them. mwah. πŸ˜­πŸ’–

and that's the whole page!! this one came from version 2.1 of pg_auto_failover, dated Jan 18, 2025. go forth and check your replication quorum, you main character. πŸŽ€βœ¨πŸ«Ά

πŸ“¦ where this page comes from