PG_AUTOCTL CONFIG CHECK(1)
β¨ PG_AUTOCTL CONFIG CHECK(1) β¨
okay bestie, welcome to the pg_autoctl config check page, which lives in the pg_auto_failover manual. it's literally the vibe check for your node setup π
πΈ NAME πΈ
pg_autoctl config check β pg_autoctl config check
pg_autoctl config check β Check pg_autoctl configuration
(no cap, it says it twice, and honestly? iconic.)
π¦ SYNOPSIS π¦
this command runs a very basic list of sanity checks on your pg_autoctl node setup, and by "very basic" we mean it, bestie, it's not doing a whole forensic audit π«Ά
usage: pg_autoctl config check [ --pgdata ] [ --json ]
--pgdata path to data directory
--json output data in the JSON format
π OPTIONS π
--pgdataβ where the Postgres node you're managing locally keeps its little home. defaults to the env varPGDATA. also: use--monitorwhen you want to connect to a monitor from anywhere, rather than the monitor URI that a local Postgres node managed withpg_autoctlis using. β¨--jsonβ outputs the data in JSON format. that's it, that's the whole flag. π
π ENVIRONMENT π
PGDATAPostgres directory location. can be used instead of the--pgdataoption. πPG_AUTOCTL_MONITORPostgres URI for connecting to the monitor node β can be used instead of the--monitoroption.XDG_CONFIG_HOMEthepg_autoctlcommand stores its configuration files in the standard placeXDG_CONFIG_HOME. see the XDG Base Directory Specification. π¦XDG_DATA_HOMEthepg_autoctlcommand stores its internal states files in the standard placeXDG_DATA_HOME, which defaults to~/.local/share. see the XDG Base Directory Specification. π¦
β EXAMPLES β
here's what a good run looks like, and ngl, it's giving "everything is fine and we love that for us":
$ pg_autoctl config check --pgdata node1
18:37:27 63749 INFO Postgres setup for PGDATA "/Users/dim/dev/MS/pg_auto_failover/tmux/node1" is ok, running with PID 5501 and port 99698
18:37:27 63749 INFO Connection to local Postgres ok, using "port=5501 dbname=demo host=/tmp"
18:37:27 63749 INFO Postgres configuration settings required for pg_auto_failover are ok
18:37:27 63749 WARN Postgres 12.1 does not support replication slots on a standby node
18:37:27 63749 INFO Connection to monitor ok, using "postgres://autoctl_node@localhost:5500/pg_auto_failover?sslmode=prefer"
18:37:27 63749 INFO Monitor is running version "1.5.0.1", as expected
pgdata: /Users/dim/dev/MS/pg_auto_failover/tmux/node1
pg_ctl: /Applications/Postgres.app/Contents/Versions/12/bin/pg_ctl
pg_version: 12.3
pghost: /tmp
pgport: 5501
proxyport: 0
pid: 99698
is in recovery: no
Control Version: 1201
Catalog Version: 201909212
System Identifier: 6941034382470571312
Latest checkpoint LSN: 0/6000098
Postmaster status: ready
not me pointing out that lil WARN in the middle β Postgres 12.1 does not support replication slots on a standby node. the check will still run, it just tells you the tea. π
π AUTHOR π
Microsoft
π COPYRIGHT π
Copyright (c) Microsoft Corporation. All rights reserved.
and that's the whole page, bestie!! π«Ά this was version 2.2 of the pg_auto_failover manual, dated Apr 07, 2025 β go forth, run your config check, and may your postmaster status always be ready πβ¨
π¦ where this page comes from
- debian trixie: pg-auto-failover-cli 2.2-2 Β· PostgreSQL
- ubuntu questing: pg-auto-failover-cli 2.2-2
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms