PG_AUTOCTL DROP MONITOR(1)

💖 pg_autoctl drop monitor — from the pg_auto_failover manual set

okay bestie, so this is the page for pg_autoctl drop monitor. yes, the whole manual is pg_auto_failover, and this is the lil corner of it that handles yeeting a monitor. let's get into it 🫶

---

✨ NAME ✨

pg_autoctl drop monitor — pg_autoctl drop monitor

pg_autoctl drop monitor — Drop the pg_auto_failover monitor

🎀 SYNOPSIS 🎀

So this command lets you review all the replication settings of a given formation (and yeah, it defaults to 'default' as usual):

usage: pg_autoctl drop monitor [ --pgdata --destroy ]

--pgdata      path to data directory
--destroy     also destroy Postgres database

👑 OPTIONS 👑

• --pgdata — where the Postgres node that's being managed locally lives. It defaults to the environment variable PGDATA. And psst: use --monitor to connect to a monitor from literally anywhere, instead of the monitor URI that a local Postgres node managed with pg_autoctl would use.
• --destroy — by default, the pg_autoctl drop monitor commands do not remove the Postgres database for the monitor. But when you throw --destroy in there, the Postgres installation gets deleted too. 😭 so like, be sure, bestie.

🌈 ENVIRONMENT 🌈

• PGDATA — Postgres directory location. You can use this instead of the --pgdata 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.
• 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.

💜 AUTHOR 💜

Microsoft

🌸 COPYRIGHT 🌸

Copyright (c) Microsoft Corporation. All rights reserved.

---

no cap, that's the whole page. go drop that monitor (or don't, it's your data directory 💀)

version 2.2 · Apr 07, 2025 — mwah, that's a wrap, ily, go be a main character in your own cluster 💅✨🦋