repmgr daemon status is not documented
Closed this issue · 2 comments
gclough commented
repmgr daemon status
is not documented in the help:
postgres ~/$ repmgr --help
repmgr: replication management tool for PostgreSQL
Usage:
...
repmgr [OPTIONS] daemon {start|stop}
...
postgres ~/$ repmgr daemon --help
repmgr: replication management tool for PostgreSQL
Usage:
repmgr [OPTIONS] daemon start
repmgr [OPTIONS] daemon stop
DAEMON START
"daemon start" attempts to start repmgrd on the local node
--dry-run check prerequisites but don't start repmgrd
-w/--wait wait for repmgrd to start (default: 15 seconds)
--no-wait don't wait for repmgrd to start
DAEMON STOP
"daemon stop" attempts to stop repmgrd on the local node
--dry-run check prerequisites but don't stop repmgrd
-w/--wait wait for repmgrd to stop (default: 15 seconds)
--no-wait don't wait for repmgrd to stop
repmgr home page: <https://repmgr.org/>
But the command itself works:
postgres ~/$ repmgr daemon status
ID | Name | Role | Status | Upstream | repmgrd | PID | Paused? | Upstream last seen
----+-----------------------------+---------+-----------+-----------------------------+---------+-------+---------+--------------------
1 | lxlabvmcdb01.linuxdev.local | standby | running | lxlabvmcdb02.linuxdev.local | running | 7269 | no | 1 second(s) ago
2 | lxlabvmcdb02.linuxdev.local | primary | * running | | running | 13026 | no | n/a
ibarwick commented
Thanks for the report; this is intentional, as we renamed the previous repmgr daemon ...
commands to repmgr service ...
in repmgr 5.0 (as daemon
is specific to the local node), but left the old invocations for backwards compatibility. See: https://repmgr.org/docs/5.0/release-5.0.html#id-1.7.6.6.3
gclough commented
OK, my bad... sorry about that!